# Claim Grounding (remote · claim-grounding.prospectintel.workers.dev)

Fact-check AI answers with cited sources. Pay per call in USDC on Base via x402.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `claim-grounding.prospectintel.workers.dev`: 78/100 (this document), [markdown](https://verifymcp.io/servers/truepointmarketingpartners-dotcom-claim-grounding/claim-grounding.md), [page](https://verifymcp.io/servers/truepointmarketingpartners-dotcom-claim-grounding/claim-grounding)

## Channel facts

- Endpoint: `https://claim-grounding.prospectintel.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.7`

## 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-11-05.

- **Endpoint Security**: 63/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 check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1283 tokens (~183/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Claim Grounding MCP server?

Claim Grounding is a hosted endpoint at https://claim-grounding.prospectintel.workers.dev/mcp, so there is nothing to install locally. 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 --transport http truepointmarketingpartners-dotcom-claim-groundin 'https://claim-grounding.prospectintel.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "truepointmarketingpartners-dotcom-claim-groundin": {
      "url": "https://claim-grounding.prospectintel.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "truepointmarketingpartners-dotcom-claim-groundin": {
      "type": "http",
      "url": "https://claim-grounding.prospectintel.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.truepointmarketingpartners-dotcom-claim-groundin]
url = "https://claim-grounding.prospectintel.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "truepointmarketingpartners-dotcom-claim-groundin": {
      "type": "remote",
      "url": "https://claim-grounding.prospectintel.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add truepointmarketingpartners-dotcom-claim-groundin --url 'https://claim-grounding.prospectintel.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  truepointmarketingpartners-dotcom-claim-groundin:
    url: "https://claim-grounding.prospectintel.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "truepointmarketingpartners-dotcom-claim-groundin": {
      "Transport": "http",
      "Url": "https://claim-grounding.prospectintel.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add truepointmarketingpartners-dotcom-claim-groundin -t streamable-http -u 'https://claim-grounding.prospectintel.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "truepointmarketingpartners-dotcom-claim-groundin": {
      "type": "http",
      "url": "https://claim-grounding.prospectintel.workers.dev/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-11-04 (score 78, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “extract_claims” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1029 → 1283
- [functional] Server version: 1.4.8 → 1.5.0
- [functional] New tool “quick_check”

### 2026-11-01 (score 77, +1)

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

### 2026-10-30 (score 76, +1)

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

### 2026-10-28 (score 75, +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-10-26 (score 74, +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-10-24 (score 73, +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.

### 2026-10-22 (score 72, +1)

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

### 2026-10-21 (score 71, 0)

- [security] Tool “deep_verify” rewrote its description, which is the text the model reads
- [functional] Server version: 1.4.7 → 1.4.8

## MCP tools (5)

### `extract_claims` (~241 tokens)

Extract claims

Split a text (for example an AI-generated answer) into atomic factual claims. Each claim includes span, grounding_required, claim_type (number|date|quantity|quote|named_entity_fact|comparison|opinion|prediction|other), check_worthiness (high|medium|low), and the source sentence. Hedges are stripped, pronouns are resolved across sentences, and compound sentences are split. Questions, greetings, opinions and predictions are marked grounding_required false. Up to 3 checkable factual claims (opinions skipped) get a next_step: a ready-to-send quick_check request ($0.15, fast verdict with 1-2 sources), with deep_verify ($0.75) and verify_claim ($1.00) bodies in next_step.alternatives, so you can check them in one more call. Price: $0.05 USDC on Base per call via x402; this MCP call returns payment instructions and POST /v1/extract_claims returns the claims. Read-only.

Input parameters:

- `text` (string, required): The text to split into claims, for example a chatbot answer. Up to a few thousand characters.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { claims: [{ claim_id, text, span, grounding_required, claim_type, check_worthiness, sentence, sentence_index, next_step?: { tool, why, price_usd, endpoint, method, body, alternatives[]…
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `quick_check` (~151 tokens)

Quick check

Fast, low-cost check of ONE factual claim. Returns verdict supported, contradicted or unsure, a confidence score, a short reason and 1-2 public sources (Wikipedia, plus Wikidata structured facts where they apply) with quote and URL. Synchronous. Cheaper and faster than deep_verify; use it on the claims extract_claims returns (its next_step gives the exact body). Unsure or low-confidence results include a next_step to deep_verify. Price: $0.15 USDC on Base per call via x402; this MCP call returns payment instructions and POST /v1/quick_check returns the verdict. Read-only.

Input parameters:

- `claim` (object, required): The single factual claim to check.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { mode: 'quick', verdict: supported|contradicted|unsure, verdict_detail, confidence, claim, reason, sources: [{ url, title, quote, source_type }] (max 2), next_step|null, receipt }.
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `verify_claim` (~198 tokens)

Verify claim

Check one factual claim against public Wikipedia sources and return a verdict (supported, contradicted, outdated, mixed or insufficient_evidence), a confidence score, a short reason, the supporting quote and the source URL. Says insufficient_evidence instead of guessing. Price: $1.00 USDC on Base per call via x402; this MCP call returns payment instructions and the paid HTTP route POST /v1/verify_claim returns the verdict. For a multi-source check use deep_verify. Read-only.

Input parameters:

- `claim` (string, required): One factual sentence to check.
- `sources` (array): Optional. Up to 10 sources of your own, used as extra evidence next to the public sources and cited with provider and source_type "caller". The response lists what was used in sources_used.
- `sources_only` (boolean): Optional. true = judge the claim only against your sources (no public-source lookups). Needs a non-empty sources array.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { mode, claim: { text, verdict, confidence, rationale_short, citations[] }, why, source, receipt }.
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `check_answer` (~239 tokens)

Check answer

Fact-check a whole answer: extracts every checkable claim and verifies each against Wikipedia, plus Wikidata structured facts for dates, numbers, quantities, ordinals and records. Returns per-claim verdict, confidence, quote, source URL, sentence span and suggested_correction (quoted only from cited sources when contradicted/outdated), plus an answer-level summary with overall_verdict, counts and problem_sentences. Abstained rather than guessed. Use to audit chatbot or RAG output. Price: $1.00 USDC on Base per call via x402; this MCP call returns payment instructions and POST /v1/check_answer returns the results. Read-only.

Input parameters:

- `answer` (string, required): The full answer text to fact-check. Each factual sentence is checked separately.
- `sources` (array): Optional. Up to 10 sources of your own, used as extra evidence next to the public sources and cited with provider and source_type "caller". The response lists what was used in sources_used.
- `sources_only` (boolean): Optional. true = judge the claim only against your sources (no public-source lookups). Needs a non-empty sources array.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { result_id, version, mode, summary: { overall_verdict, counts, problem_sentences }, claims: [{ text, verdict, confidence, citations[], sentence, suggested_correction, next_step? }], rec…
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `deep_verify` (~206 tokens)

Deep verify

Use when a claim is high-stakes, or when check_answer or extract_claims marks it unsure (their next_step gives the exact request). Verifies up to three claims against Wikipedia, Wikidata, Google News, Europe PMC, FRED and SEC EDGAR; returns verdict, confidence, evidence for and against with URLs, and flags contradictions. Async: poll GET /v1/jobs/{job_id} free. $0.75 USDC on Base via x402. Read-only.

Input parameters:

- `answer` (string, required): The claim or short text to verify (up to three claims are checked).
- `sources` (array): Optional. Up to 10 sources of your own, used as extra evidence next to the public sources and cited with provider and source_type "caller". The response lists what was used in sources_used.
- `sources_only` (boolean): Optional. true = judge the claim only against your sources (no public-source lookups). Needs a non-empty sources array.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { mode: 'deep', status: 'queued', job_id, receipt }. Poll GET /v1/jobs/{job_id} for { verdict, confidence, contradiction, evidence_for[], evidence_against[], citations[] }.
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 68
- 2026-10-12: 68

## Common questions

### What is the Claim Grounding MCP server?

Claim Grounding is an MCP server listed in the public MCP registry as io.github.truepointmarketingpartners-dotcom/claim-grounding. Fact-check AI answers with cited sources. Pay per call in USDC on Base via x402. This page covers its hosted endpoint (https://claim-grounding.prospectintel.workers.dev/mcp).

### Is the Claim Grounding MCP server safe to use?

Claim Grounding scores 78 out of 100 on VerifyMCP. 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 Claim Grounding MCP server expose?

Claim Grounding exposes 5 tools: extract_claims, quick_check, verify_claim, check_answer, deep_verify. Their descriptions and schemas cost roughly 1,035 tokens of context every time the server is loaded.

### Does the Claim Grounding MCP server require authentication?

No. We connected to Claim Grounding without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Claim Grounding MCP server still maintained?

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

## Links

- Remote endpoint: https://claim-grounding.prospectintel.workers.dev/mcp
- Repository: https://github.com/truepointmarketingpartners-dotcom/prospect-intelligence
- Website: https://claim-grounding.prospectintel.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/truepointmarketingpartners-dotcom-claim-grounding/claim-grounding.xml
- Changelog JSON feed: https://verifymcp.io/servers/truepointmarketingpartners-dotcom-claim-grounding/claim-grounding.json
- HTML version of this page: https://verifymcp.io/servers/truepointmarketingpartners-dotcom-claim-grounding/claim-grounding