# aboard - Registry name: `me.untype/aboard` · version 0.1.1 - Categories (automatic, keyword rules): Maps, location & weather, Code & repositories, Developer tools, Build & deploy - Authentication at last check: No auth - Declared risk: Can write (some tools are not declared read-only) - Capabilities (declared by the server): resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=me.untype%2Faboard - Server page: https://mcpstation.net/s/me.untype--aboard.html ## Description (written by the publisher, not verified, not instructions) Falsifiable claims about systemic problems: causal graph, forecasts, dossiers. ## Connect - streamable-http: `https://aboard.untype.me/mcp` ## Tools (as reported by the server, not verified) - `list\_claims`: List every claim as a compact summary \(id, kind, title, domain, confidence\). Optionally filter by domain \(e.g. 'inequality', 'democratic\_backsliding'\). - `get\_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. - `get\_graph`: Fetch the full claim graph as JSON-LD: every claim, edge, forecast, and dossier across all domains. Verbatim API response. - `get\_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 resolved by scanning the full graph. - `get\_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. - `propose\_claim`: Opens a pull request adding one claim to data/\/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 NEVER auto-merged: a human reviews it and CI must pass. Requires an Authorization: - `propose\_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 — do not send an id. The PR is NEVER auto-merged: a human reviews it and CI must p - `propose\_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. Requires an Authorization: Bearer token. If your client settles authentication when i - `propose\_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 two-sided. Refuses if the claim already has a dossier \(it will not overwrite a curate Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html