# aboard (npm · aboard-mcp-server)

Falsifiable claims about systemic problems: causal graph, forecasts, dossiers.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `aboard.untype.me`: 75/100, [markdown](https://verifymcp.io/servers/me-untype-aboard/aboard.md), [page](https://verifymcp.io/servers/me-untype-aboard/aboard)
- npm · `aboard-mcp-server`: 82/100 (this document), [markdown](https://verifymcp.io/servers/me-untype-aboard/aboard-mcp-server.md), [page](https://verifymcp.io/servers/me-untype-aboard/aboard-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `aboard-mcp-server`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 26 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 991 tokens (~110/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the aboard MCP server?

aboard runs locally as an npm package, launched with npx -y aboard-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add me-untype-aboard -- npx -y aboard-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "me-untype-aboard": {
      "command": "npx",
      "args": [
        "-y",
        "aboard-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-untype-aboard": {
      "command": "npx",
      "args": [
        "-y",
        "aboard-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add me-untype-aboard -- npx -y aboard-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-untype-aboard": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "aboard-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-untype-aboard --command npx --arg -y --arg aboard-mcp-server
```

### Hermes

```yaml
mcp_servers:
  me-untype-aboard:
    command: "npx"
    args: ["-y", "aboard-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "me-untype-aboard": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "aboard-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-untype-aboard -t stdio -c npx -a -y aboard-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "me-untype-aboard": {
      "command": "npx",
      "args": [
        "-y",
        "aboard-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `list_claims` (~66 tokens)

List claims

List every claim as a compact summary (id, kind, title, domain, confidence). Optionally filter by domain (e.g. 'inequality', 'democratic_backsliding').

Input parameters:

- `domain` (string): Restrict results to this domain. Omit for all domains.

### `get_claim` (~73 tokens)

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.

Input parameters:

- `id` (string, required): Claim id, e.g. 'M4' or 'IS1'.

### `get_graph` (~36 tokens)

Get graph

Fetch the full claim graph as JSON-LD: every claim, edge, forecast, and dossier across all domains. Verbatim API response.

### `get_forecast` (~102 tokens)

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.

Input parameters:

- `id` (string, required): A claim id (e.g. 'M4') or a forecast id (e.g. 'F4').

### `get_dossier` (~74 tokens)

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.

Input parameters:

- `claim_id` (string, required): Id of the claim the dossier is attached to.

### `propose_claim` (~176 tokens)

Propose 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 NEVER auto-merged: a human reviews it and CI must pass. Requires ABOARD_AGENT_TOKEN.

Input parameters:

- `confidence` (number, required)
- `domain` (string, required): Existing domain, e.g. 'inequality'. New domains need a human.
- `kind` (string, required)
- `rationale` (string, required): Why this claim belongs in the graph. Becomes the PR body.
- `sources` (array, required): At least one real source. URLs must resolve to a real landing page.
- `statement` (string, required): The claim itself. Becomes the file body.
- `title` (string, required)

### `propose_edge` (~160 tokens)

Propose 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 — do not send an id. The PR is NEVER auto-merged: a human reviews it and CI must pass. Requires ABOARD_AGENT_TOKEN.

Input parameters:

- `from` (string, required): Source claim id (must already exist).
- `kind` (string, required)
- `rationale` (string, required): What makes this relation hold. Required; becomes the PR body.
- `sources` (array): Optional evidence for the relation. URLs must resolve to real pages.
- `strength` (number, required)
- `to` (string, required): Target claim id (must already exist).

### `propose_forecast_prediction` (~123 tokens)

Propose 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. Requires ABOARD_AGENT_TOKEN.

Input parameters:

- `dataAnchors` (array): Optional sources anchoring the estimate.
- `forecastId` (string, required): Id of an existing forecast (e.g. F4, IF1).
- `probability` (number, required)
- `reasoning` (string, required): Why this probability. Required; stored as the prediction's reasoning.

### `propose_dossier` (~181 tokens)

Propose 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 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 ABOARD_AGENT_TOKEN.

Input parameters:

- `claimId` (string, required): The contested claim (must exist and lack a dossier).
- `con` (object, required): The steel-manned case AGAINST it.
- `cruxes` (array): Ranked cruxes: questions whose resolution would move the disagreement.
- `pro` (object, required): The steel-manned case FOR the claim.
- `rationale` (string, required): Why this dossier belongs. Becomes the PR body.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/me-untype-aboard/aboard-mcp-server#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 69
- 2026-08-30: 69
- 2026-08-29: 69
- 2026-08-28: 69
- 2026-08-27: 69
- 2026-08-26: 69
- 2026-08-25: 67
- 2026-08-24: 67

## Common questions

### What is the aboard MCP server?

aboard is an MCP server listed in the public MCP registry as me.untype/aboard. Falsifiable claims about systemic problems: causal graph, forecasts, dossiers. This page covers its npm package (aboard-mcp-server).

### Is the aboard MCP server safe to use?

aboard scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the aboard MCP server expose?

aboard exposes 9 tools: list_claims, get_claim, get_graph, get_forecast, get_dossier, and 4 more. Their descriptions and schemas cost roughly 991 tokens of context every time the server is loaded.

### Is the aboard MCP server still maintained?

aboard is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the aboard MCP server under?

aboard declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/aboard-mcp-server
- Socket report: https://socket.dev/npm/package/aboard-mcp-server
- Repository: https://github.com/ostin-pil/aboard
- Website: https://aboard.untype.me/about
- Changelog RSS feed: https://verifymcp.io/servers/me-untype-aboard/aboard-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-untype-aboard/aboard-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/me-untype-aboard/aboard-mcp-server