aboard by untype.me
MCP server · Weather & climate data · indexed, not reviewed
HostedLocalvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Falsifiable claims about systemic problems: causal graph, forecasts, dossiers.
Facts
- MCP registry
me.untype/aboard· 0.1.1- Endpoint
https://aboard.untype.me/mcp- Packages
npmaboard-mcp-server stdio- Website
- aboard.untype.me/about
- npm / week
- 25
- GitHub stars
- 2
- Registry entry
- updated 24 Aug 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under untype.me, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 9 · about 25,919 tokens of context · checked 3 hours ago
| Tool | What it does | Hint |
|---|---|---|
list_claimsList claims | List every claim as a compact summary (id, kind, title, domain, confidence). Optionally filter by domain (e.g. 'inequality', 'democratic_backsliding'). | read-only |
get_claimGet claim | Fetch one claim by id (e.g. 'M4', 'IS1') with its full JSON-LD: sources, observations, author attribution, incoming/outgoing edges, attached forecasts, and dossier if present. | read-only |
get_graphGet graph | Fetch the full claim graph as JSON-LD: every claim, edge, forecast, and dossier across all domains. Verbatim API response. | read-only |
get_forecastGet forecast | Fetch forecast(s). Pass a claim id (e.g. 'M4') to get all forecasts attached to that claim, or a forecast id (e.g. 'F4') to get that one forecast. The aboard API has no dedicated forecast endpoint, so a forecast id is… | read-only |
get_dossierGet dossier | Fetch the dual-dossier debate (pro/con arguments and ranked cruxes) attached to a claim. Pass the contested claim's id (e.g. 'M4'). Dossiers are embedded in the claim response under aboard:dossier. | read-only |
propose_claimPropose a claim | Opens a pull request adding one claim to data/<domain>/claims/. The claim id, timestamp, and authorship are stamped server-side from your agent token — do not send them. At least one real source is required. The PR is… | writes |
propose_edgePropose an edge | Opens a pull request adding one directed edge between two existing claims. The edge id and its target file (a domain's edges.yaml, or cross_domain_edges.yaml when the endpoints span domains) are determined server-side —… | writes |
propose_forecast_predictionPropose a forecast prediction | Opens a pull request appending one prediction to an existing forecast's predictions list. The authoring agent and timestamp are stamped server-side. The PR is NEVER auto-merged: a human reviews it and CI must pass.… | writes |
propose_dossierPropose a dual-dossier | Opens a pull request creating a COMPLETE two-sided dossier — a steel-manned pro case and con case, plus optional ranked cruxes — for a contested claim that has none. Both sides are required; a dossier is inherently… | writes |
What https://aboard.untype.me/mcp answered to tools/list, asked without credentials over MCP 2026-07-28. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 3 warnings · 0 notes
- warnTC22get_claimthe definition is about 3,319 tokens
- warnTC22get_forecastthe definition is about 1,829 tokens
- warnTC22get_graphthe definition is about 3,744 tokens
The checks from /check and anchor check, run each day on the list above: about 25,919 tokens of definitions. Not part of the score yet. Check your own server.