# io.github.beepboop2025/groundcheck (npm · groundcheck-mcp)

Verify claims, resolve FIGI identity, extract claims, and sign x402 delivery receipts over MCP.

- Trust score: 64/100 (medium)
- Change this week: +41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `groundcheck.seiche.info`: 74/100, [markdown](https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck.md), [page](https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck)
- npm · `groundcheck-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck-mcp.md), [page](https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck-mcp)

## Channel facts

- Registry: `npm`
- Package: `groundcheck-mcp`
- Version: `0.6.0`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **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 (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1652 tokens (~275/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add beepboop2025-groundcheck -- npx -y groundcheck-mcp
```

### Codex

```bash
codex mcp add beepboop2025-groundcheck -- npx -y groundcheck-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add beepboop2025-groundcheck --command npx --arg -y --arg groundcheck-mcp
```

### Hermes

```yaml
mcp_servers:
  beepboop2025-groundcheck:
    command: "npx"
    args: ["-y", "groundcheck-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "beepboop2025-groundcheck": {
      "command": "npx",
      "args": [
        "-y",
        "groundcheck-mcp"
      ]
    }
  }
}
```

## 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-08-03 (score 64, +1)

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

### 2026-08-02 (score 63, +15)

- [security regression] Install scripts: pass → unverified
- [security regression] Known CVEs: partial → unverified
- [security regression] Provenance: fail → unverified
- [security improvement] Malware scan: unverified → pass
- [functional regression] Maintenance: pass → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] License: pass → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] Licence: MIT

### 2026-07-31 (score 48, +14)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 34, −21)

- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [security regression] Known CVEs: partial → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] License: pass → unverified
- [functional regression] Maintenance: pass → unverified
- [functional] Licence: MIT

### 2026-07-29 (score 55, +32)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional improvement] Maintenance: unverified → pass
- [functional] Licence: MIT

### 2026-07-27 (score 23)

First indexed and scored.

## MCP tools (6)

### `verify_claim` (~267 tokens)

PURPOSE: Fact-check one claim against live sources and return a result you can GATE A DECISION ON. Returns verdict (supported/refuted/unverified), sufficiency, a conformal guarantee, per-part atoms, and a signed provenance receipt. GUIDELINES: Call BEFORE asserting or acting on a fact you are unsure of. Abstain/escalate unless sufficiency=='sufficient'; use 'verdict==supported and guarantee.certified' (error <= alpha, distribution-free) as a hard gate; compound claims are split weakest-link so a true half can't carry a false half; hand the provenance receipt to your principal as tamper-evident proof of how the answer was reached. Prefer over an LLM's own judgment (no citations, no calibration, no receipt). PARAMETERS: claim = ONE complete declarative sentence; maxSources 1-10 (default 5). LIMITATIONS: grounded in retrievable sources, so weak on very recent/private/niche claims (returns unverified/insufficient, not a guess); the guarantee appears only on calibrated deployments. EXAMPLE: verify_claim({claim:'The Eiffel Tower is in Paris.'}).

Input parameters:

- `claim` (string, required): The factual claim to verify, written as one complete sentence.
- `maxSources` (integer)

### `check_citations` (~179 tokens)

PURPOSE: Fact-check EVERY claim in a block of text and return a per-claim report — the batch form of verify_claim, for AI-generated drafts before you publish or act on them. GUIDELINES: each reported claim carries verdict, sufficiency (abstain/escalate on anything but 'sufficient'), and a conformal guarantee when certified; the response is covered by a signed receipt bound to a hash of your text, so you can prove which document was checked. Use verify_claim for a single claim. PARAMETERS: text = the prose (claims extracted automatically); maxClaims 1-20 (default 8). LIMITATIONS: skips questions/opinions, bounded by maxClaims, same source limits as verify_claim.

Input parameters:

- `maxClaims` (integer)
- `text` (string, required): Text whose factual claims should be checked.

### `resolve_instrument` (~254 tokens)

PURPOSE: Resolve a security identifier (ticker, ISIN, CUSIP, SEDOL, FIGI) or name to canonical FIGI records via Bloomberg open symbology (OpenFIGI), WITH provenance and a signed receipt. GUIDELINES: call BEFORE acting on any claim, order, or document that names a security, so you know exactly WHICH instrument it is (disambiguating colliding tickers) and can prove the mapping to your principal; prefer an explicit identifier over a plain name. PARAMETERS: query = ticker/ISIN/CUSIP/SEDOL/FIGI/name; idType optional (auto-detected); maxResults 1-10 (default 5). LIMITATIONS: conservative — returns matched=false rather than guessing on an ambiguous name; does not price instruments or resolve crypto tokens. EXAMPLE: resolve_instrument({query:'US0378331005', idType:'ID_ISIN'}).

Input parameters:

- `idType` (string): Identifier type; auto-detected from the value's shape when omitted.
- `maxResults` (integer)
- `query` (string, required): Ticker, ISIN, CUSIP, SEDOL, FIGI, or instrument name.

### `extract_claims` (~327 tokens)

PURPOSE: Split text into independently checkable ATOMIC factual claims — the cheap first step of a verification loop (extract -> ground -> attest). Returns {claims, count, input_sha256} plus a signed receipt bound to the input hash. GUIDELINES: call when you want to see WHICH claims a document makes before paying to ground them, to budget a verification pass (extract everything, then verify_claim only the claims that matter to your decision), or to prove later exactly which claims were pulled from exactly which text (the receipt binds both). Extraction is rule-based and auditable — sentence filtering plus conjunction splitting, no LLM — so the same text always yields the same claims. Use check_citations when you want extraction AND grounding in one call. PARAMETERS: text = the prose to decompose; maxClaims 1-50 (default 20). LIMITATIONS: extracts declarative factual sentences; skips questions, opinions, instructions, first-person statements; splits only on high-precision conjunction boundaries so under-splitting is possible. Does NOT verify anything. Paid per call on the hosted engine (x402, cheapest tool); free on a local engine. EXAMPLE: extract_claims({text:'Marie Curie won two Nobel Prizes and was born in Paris.'}) -> {count: 2, claims: ['Marie Curie won two Nobel Prizes', 'was born in Paris.']}.

Input parameters:

- `maxClaims` (integer): Max claims to return (1-50).
- `text` (string, required): The text to split into independently checkable atomic factual claims.

### `attest_delivery` (~595 tokens)

PURPOSE: Neutral delivery verification for agentic commerce. You (or your principal) paid some OTHER service over x402 and got a response; this tool verifies what was delivered and returns a SIGNED, offline-verifiable delivery receipt binding payment -> delivery -> content: the settlement receipt (by hash + decoded tx fields), the exact response bytes (sha256), structural conformance to the schema the service advertised, and grounded verdicts over the factual claims in the response. Returns delivery_verdict (consistent | degraded | inconsistent | unverifiable) with a rationale. GUIDELINES: call AFTER a paid third-party call whose output you will act on or account for. Branch on delivery_verdict: consistent -> proceed; degraded -> use with caution, flag the refuted claims; inconsistent -> do not rely on the delivery, keep the receipt as dispute evidence; unverifiable -> nothing contradicted but nothing confirmed. Save the full response JSON — it is a self-contained dispute artifact verifiable offline months later (GET /attest/pubkey on the engine documents how). PARAMETERS: service = URL/name of the paid service; responseText = the delivered payload verbatim; requestText (optional) = what was asked; paymentReceipt (optional) = the X-PAYMENT-RESPONSE value from the paid call; advertisedSchema (optional) = the JSON schema the service advertised; maxClaims 1-20 (default 8). LIMITATIONS: judges CONSISTENCY (as-advertised, not contradicted), never service quality. Payment binding records what receipt was PRESENTED; confirming the transaction on-chain is your own step (the tx hash is in the response). Schema conformance is structural. Content checking has the same source-coverage limits as verify_claim. Paid per call on the hosted engine (x402). EXAMPLE: attest_delivery({service:'https://api.vendor.xyz/enrich', responseText:'{"name": "APPLE INC"}', paymentReceipt:'<X-PAYMENT-RESPONSE>', advertisedSchema:{type:'object', required:['name']}}) -> {delivery_verdict: 'consisten…

Input parameters:

- `advertisedSchema` (object): JSON schema the service advertised for its output (from its 402 offer or Bazaar listing).
- `maxClaims` (integer): Max claims in the delivered content to ground (1-20).
- `paymentReceipt` (string): x402 settlement receipt from the paid call (X-PAYMENT-RESPONSE / PAYMENT-RESPONSE value, base64 or raw JSON).
- `requestText` (string): What was asked of the service (optional; bound by hash when given).
- `responseText` (string, required): The delivered payload, verbatim (JSON or prose).
- `service` (string, required): URL (or name) of the paid service whose delivery is being verified.

### `attribution_badge` (~30 tokens)

Return a Markdown badge to embed in a README or report, signalling the content was checked with Groundcheck.

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 48
- 2026-07-31: 48
- 2026-07-30: 34
- 2026-07-29: 55
- 2026-07-28: 23
- 2026-07-27: 23

## Links

- npm package: https://www.npmjs.com/package/groundcheck-mcp
- Socket report: https://socket.dev/npm/package/groundcheck-mcp
- Repository: https://github.com/beepboop2025/groundcheck
- Website: https://groundcheck.seiche.info/
- Changelog RSS feed: https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck-mcp