aboard is answering right now. Last checked 7 min ago. 46 installs a week from npm. It exposes 9 tools.
Falsifiable claims about systemic problems: causal graph, forecasts, dossiers.
The linked repository no longer exists on GitHub — it was deleted or made private.
Installs per day
peak 10 · avg 4 · +68% w/w
a month agotoday
Uptime history
91 days of history · worst day 93%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
205 ms
Response time
average over 24h
46
Installs / week
npm and PyPI
What changed 9
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
22 Aug
a tool changed version
11 Aug
4 tools changed the parameters they ask for
propose_claim, propose_dossier, propose_edge and 1 more
9 Aug
4 tools changed the parameters they ask for
propose_claim, propose_dossier, propose_edge and 1 more
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add aboard --transport http https://aboard.untype.me/mcpSettings → Connectors → Add custom connector, then paste this address
https://aboard.untype.me/mcp~/.codex/config.toml
[mcp_servers.aboard]
url = "https://aboard.untype.me/mcp".cursor/mcp.json
{
"mcpServers": {
"aboard": {
"url": "https://aboard.untype.me/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"aboard": {
"type": "http",
"url": "https://aboard.untype.me/mcp"
}
}
}Available tools 9
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
propose
propose_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 NEVER auto-merged: a human reviews it and CI must pass. Requires an Authorization: Bearer token. If your client settles authentication when it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.
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 curated one). The authoring agent is stamped server-side. NEVER auto-merged. Requires an Authorization: Bearer token. If your client settles authentication when it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.
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 pass. Requires an Authorization: Bearer token. If your client settles authentication when it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.
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 it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.
claim
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.
claims
list_claims
List every claim as a compact summary (id, kind, title, domain, confidence). Optionally filter by domain (e.g. 'inequality', 'democratic_backsliding').
dossier
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.
forecast
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.
graph
get_graph
Fetch the full claim graph as JSON-LD: every claim, edge, forecast, and dossier across all domains. Verbatim API response.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://aboard.untype.me/mcp | streamable-http | answering | 206 ms | 7 min ago |
Alternatives to aboard
same job, measured the same wayBrain Protocol
by seritalien
Verifiable Memory for AI Agents — knowledge graph, FTS, Starknet proofs, local or cloud
RoboSystems
by robosystems
Accounting knowledge graphs: SEC XBRL filings, QuickBooks ledgers, reports and forecasts over MCP.
ClipGrab
by ulebule
Save the system clipboard image to a PNG or JPG file for AI agents.
glin
by akashchatterjee
Exactly explainable classifiers for agents: train, tune, predict, explain on CSV or Excel.
Openhuddle
by nika110
Multiplayer mode for AI coding agents: team huddles, master prompt, task board, file claims.
gen-system Understand
by hpdkhoa
Parser facts about a codebase: architecture, call graphs, control flow, effects, beliefs
Directum RX
by drxinfra
Directum RX for AI assistants: assignments, documents, boards, projects, any entity, system help
Patent Search MCP Server
by smythmyke
Patent dossiers, prosecution, claims + a legal layer (PTAB, litigation, term) + AI risk. USPTO.
aboard — questions
Answers built from our own checks of this server.
What can aboard do?
It exposes 9 tools, read directly from the server on our last check. Among them: get_claim, get_dossier, get_forecast, get_graph, list_claims, propose_claim and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is aboard working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 205 ms. The bar chart above shows every period we have measured.
Is aboard still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect aboard?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does aboard need an API key?
No. aboard completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is aboard?
It answers our handshake in 205 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use aboard?
The npm package aboard-mcp-server was installed 46 times in the last week. Week over week that is +68%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.