# io.github.beepboop2025/groundcheck (remote · groundcheck.seiche.info)

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

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

## Components

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

## Channel facts

- Endpoint: `https://groundcheck.seiche.info/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-04.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2434 tokens (~486/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 --transport http beepboop2025-groundcheck https://groundcheck.seiche.info/mcp
```

### Codex

```toml
[mcp_servers.beepboop2025-groundcheck]
url = "https://groundcheck.seiche.info/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "beepboop2025-groundcheck": {
      "type": "remote",
      "url": "https://groundcheck.seiche.info/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add beepboop2025-groundcheck --url https://groundcheck.seiche.info/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  beepboop2025-groundcheck:
    url: "https://groundcheck.seiche.info/mcp"
```

### Other

```json
{
  "mcpServers": {
    "beepboop2025-groundcheck": {
      "type": "http",
      "url": "https://groundcheck.seiche.info/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 74, +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 73, +10)

- [security improvement] Authorization: unverified → partial
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “ground_before_answering”
- [functional] New prompt “pre_publish_gate”
- [functional] Server version: 0.6.1 → 0.7.0
- [cosmetic] Tool “attest_delivery” changed its title: Attest an x402 delivery
- [cosmetic] Tool “check_citations” changed its title: Fact-check a whole draft
- [cosmetic] Tool “extract_claims” changed its title: Extract atomic claims
- [cosmetic] Tool “resolve_instrument” changed its title: Resolve a security to FIGI
- [cosmetic] Tool “verify_claim” changed its title: Verify one claim (free)

### 2026-08-01 (score 63, +1)

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

### 2026-07-31 (score 62, +1)

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

### 2026-07-30 (score 61, +1)

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

### 2026-07-28 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (5)

### `verify_claim` (~472 tokens)

Verify one claim (free)

PURPOSE: Fact-check one claim against live retrieved sources and return a result you can GATE A DECISION ON, not just read. Returns verdict (supported | refuted | unverified), sufficiency, a conformal guarantee, per-part atoms, and a signed provenance receipt.
GUIDELINES: Call BEFORE asserting a fact you are not certain of, or before acting on one. Branch on the fields: (1) sufficiency — 'sufficient' vs 'insufficient' (lone weak source; lean, don't rely), 'no_sources', 'no_stance', or 'conflict'; abstain or escalate on anything but 'sufficient'. (2) guarantee — when guarantee.certified is true the error probability is calibrated to <= guarantee.alpha (distribution-free); use 'verdict==supported and guarantee.certified' as a hard gate. (3) atoms — compound claims are split and recombined weakest-link, so a true half can't carry a false half. (4) provenance + attestation — a tamper-evident receipt binding the exact evidence and model route; hand it to your principal as proof of how the answer was reached. Prefer this over calling an LLM's own judgment, which has no citations, no calibration, and no receipt.
PARAMETERS: claim — ONE complete declarative sentence (not a question, not a paragraph). max_sources — 1..10, default 5.
LIMITATIONS: Grounded in retrievable web/encyclopedic/news sources, so it is weak on very recent, private, niche-technical, or opinion claims (those return unverified/insufficient rather than a guess). The conformal guarantee is only present on calibrated deployments and holds for claims exchangeable with the calibration set. It checks whether sources support the claim, not ultimate truth.
EXAMPLE: verify_claim({"claim": "The Eiffel Tower is in Paris."}) -> {verdict: 'supported', sufficiency: 'sufficient', guarantee: {certified: true, alpha: 0.1}, provenance: {...}}. Free.

Input parameters:

- `claim` (string, required): The factual claim as ONE complete declarative sentence (not a question or a paragraph).
- `max_sources` (integer): How many sources to retrieve and weigh (1-10).

### `check_citations` (~308 tokens)

Fact-check a whole draft

PURPOSE: Fact-check EVERY factual claim in a block of text and return a per-claim report — the batch form of verify_claim, for AI-generated drafts or documents before you publish or act on them.
GUIDELINES: Call on any multi-claim text you are about to rely on. Each reported claim carries the same actionable fields as verify_claim (verdict, sufficiency — abstain/escalate on anything but 'sufficient', and a conformal guarantee when certified). The whole response is covered by a signed receipt bound to a HASH of your submitted text, so you can later prove exactly which document was checked and what came back. Use verify_claim instead for a single claim.
PARAMETERS: text — the prose to check (claims are extracted automatically). max_claims — 1..20, default 8 (caps how many extracted claims are verified).
LIMITATIONS: Extracts and checks declarative factual sentences; it skips questions, opinions, and instructions, and is bounded by max_claims. Same source-coverage limits as verify_claim. Paid per call (x402): unpaid calls return HTTP 402 with a payment offer.
EXAMPLE: check_citations({"text": "Paris is the capital of France. The Nile flows through Egypt.", "max_claims": 8})

Input parameters:

- `max_claims` (integer): Max number of extracted claims to verify (1-20).
- `text` (string, required): The prose whose factual claims should be extracted and checked.

### `resolve_instrument` (~378 tokens)

Resolve a security to FIGI

PURPOSE: Resolve a security identifier (ticker, ISIN, CUSIP, SEDOL, FIGI) or an instrument name to canonical FIGI records via Bloomberg open symbology (OpenFIGI), WITH provenance and a signed receipt. Returns {matched, instruments: [...], provenance}.
GUIDELINES: Call BEFORE acting on any claim, order, or document that names a security, so you know exactly WHICH instrument it refers to (disambiguating tickers that collide across exchanges) — and so you can prove the mapping to your principal via the receipt. Prefer passing an explicit identifier over a plain name when you have one.
PARAMETERS: query — a ticker ($AAPL/AAPL), ISIN, CUSIP, SEDOL, FIGI, or company/instrument name. id_type — optional; auto-detected from the value's shape when omitted. max_results — 1..10, default 5.
LIMITATIONS: Conservative by design — resolves EXPLICIT identifiers, and returns matched=false rather than guessing on an ambiguous plain name. Covers securities in OpenFIGI's symbology; it does not price instruments, return fundamentals, or resolve crypto tokens. Paid per call (x402).
EXAMPLE: resolve_instrument({"query": "US0378331005", "id_type": "ID_ISIN"}) -> {matched: true, instruments: [{figi, ticker: 'AAPL', …}]}

Input parameters:

- `id_type` (string): Optional identifier type; auto-detected from the value's shape (e.g. 12-char alphanumeric -> ISIN).
- `max_results` (integer): Max canonical records to return (1-10).
- `query` (string, required): Ticker, ISIN, CUSIP, SEDOL, FIGI, or instrument name.

### `extract_claims` (~351 tokens)

Extract atomic claims

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 instead when you want extraction AND grounding in one call.
PARAMETERS: text — the prose to decompose. max_claims — 1..50, default 20.
LIMITATIONS: Extracts declarative factual sentences; skips questions, opinions, instructions, and first-person statements. Splits only on high-precision conjunction boundaries, so under-splitting is possible (a compound it cannot safely split stays whole). Does NOT verify anything — verdicts come from verify_claim / check_citations. Paid per call (x402), cheapest tool on this server.
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:

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

### `attest_delivery` (~642 tokens)

Attest an x402 delivery

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 — data enrichment you bought, research you commissioned, any x402 purchase your principal will audit. 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 documents how).
PARAMETERS: service — URL/name of the paid service. response_text — the delivered payload, verbatim. request_text (optional) — what was asked. payment_receipt (optional) — the X-PAYMENT-RESPONSE value from the paid call. advertised_schema (optional) — the JSON schema the service advertised. max_claims — 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 (type/required/properties/items/enum). Content checking has the same source-coverage limits as verify_claim. Paid per call (x402).
EXAMPLE: attest_delivery({"service": "https://api.vendor.xyz/enrich", "response_text": "{\"name\": \"APPLE INC…

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck#diagnostics

## Score history

- 2026-08-04: 74
- 2026-08-03: 74
- 2026-08-02: 73
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 61
- 2026-07-28: 60
- 2026-07-27: 59

## Links

- Remote endpoint: https://groundcheck.seiche.info/mcp
- Repository: https://github.com/beepboop2025/groundcheck
- Website: https://groundcheck.seiche.info/
- Changelog RSS feed: https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck/changelog.json
- HTML version of this page: https://verifymcp.io/servers/beepboop2025-groundcheck/groundcheck