Claim Grounding
REMOTE · CLAIM-GROUNDING.PROSPECTINTEL.WORKERS.DEV
Fact-check AI answers with cited sources. Pay per call in USDC on Base via x402.
Available components
Last scanned (23 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- 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 security
- Schema quality: 1029 → 1283 ▼ functional
- Server version: 1.4.8 → 1.5.0 functional
- New tool “quick_check” functional
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 21 Oct 26 0
- Tool “deep_verify” rewrote its description, which is the text the model reads security
- Server version: 1.4.7 → 1.4.8 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://claim-grounding.prospectintel.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=prospectintel.workers.dev | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5608fbca9661874e0e6c6cda66de40d5 |
| SANs: prospectintel.workers.dev, *.prospectintel.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of claim-grounding.prospectintel.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://claim-grounding.prospectintel.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://claim-grounding.prospectintel.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_answer Check answer ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | 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 | yes | payment_required: pay the HTTP route with x402 to get the result. ok: result is included. |
| tool | string | yes | Tool name. |
No examples provided.
deep_verify Deep verify ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | 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 | yes | payment_required: pay the HTTP route with x402 to get the result. ok: result is included. |
| tool | string | yes | Tool name. |
No examples provided.
extract_claims Extract claims ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to split into claims, for example a chatbot answer. Up to a few thousand characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | 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 | yes | payment_required: pay the HTTP route with x402 to get the result. ok: result is included. |
| tool | string | yes | Tool name. |
No examples provided.
quick_check Quick check ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | object | yes | The single factual claim to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | 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 | yes | payment_required: pay the HTTP route with x402 to get the result. ok: result is included. |
| tool | string | yes | Tool name. |
No examples provided.
verify_claim Verify claim ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | 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 | yes | payment_required: pay the HTTP route with x402 to get the result. ok: result is included. |
| tool | string | yes | Tool name. |
No examples provided.
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.
remote · claim-grounding.prospectintel.workers.dev
claude mcp add --transport http truepointmarketingpartners-dotcom-claim-groundin 'https://claim-grounding.prospectintel.workers.dev/mcp'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.