mcpbeat Sign in

aboard MCP Server

answering

aboard is answering right now. Last checked 8 min ago. 29 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 115 · avg 4
a month agotoday
Uptime history 51 days of history · worst day 97%
51 days agonow
97.8%
Uptime 24h
89 of 91 checks
9
Tools
read from the server
271 ms
Response time
average over 24h
29
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

aboard does not always answer

Over the last week it answered 99.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add aboard --transport http https://aboard.untype.me/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "aboard": {
      "url": "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
{
  "mcpServers": {
    "aboard": {
      "url": "https://aboard.untype.me/mcp"
    }
  }
}

This one needs environment variables set before it will start: ABOARD_API_BASE_URL (Base URL of the aboard instance to read from. Defaults to the canonical deploy; set it to point the server at another instance.), ABOARD_AGENT_TOKEN (Service token issued by the aboard operator. Needed only by the four write tools, each of which opens a pull request a human must review. The five read tools need no credential.). The author declared them in the registry entry; get the values from the project itself.

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

URLTransportStateLatencyChecked
https://aboard.untype.me/mcp streamable-http answering 248 ms 8 min ago

Alternatives to aboard

same job, measured the same way
Brain Protocol
by seritalien

Verifiable Memory for AI Agents — knowledge graph, FTS, Starknet proofs, local or cloud

38 installs/wk local only
RoboSystems
by robosystems

Accounting knowledge graphs: SEC XBRL filings, QuickBooks ledgers, reports and forecasts over MCP.

answering
ClipGrab
by ulebule

Save the system clipboard image to a PNG or JPG file for AI agents.

58 installs/wk local only
Patent Search MCP Server
by smythmyke

Patent dossiers, prosecution, claims + a legal layer (PTAB, litigation, term) + AI risk. USPTO.

43 installs/wk local only
Templates
by theluckystrike

Reusable docx templates: placeholders for proposals, contracts, quotes, SOWs.

local only
Pullboard
by pullboard

Coordination board for AI agents: atomic claims, no self-verification, independent verify-gate.

answering
Perseus Ledger — verifiable, hash-chained event provenance
by perseus-computing-llc

Verifiable, hash-chained event provenance for autonomous systems. Local-first, MIT. 5 MCP tools.

131 installs/wk local only
I
TypeUI
by bergside

Design systems, UI prompts, and layout variations for AI coding tools.

answering

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 89 of 91 checks got a reply (97.8%), average response time 271 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 with the file path 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 271 ms on average, which is faster than 57% 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 29 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.