Claim Grounding MCP server
io.github.truepointmarketingpartners-dotcom/claim-groundingtruepointmarketingpartners-dotcomstreamable-httpv1.5.0Scanned
Fact-check AI answers with cited sources and quick_check. Pay per call in USDC via x402.
5 tools: 5 change things.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Claim Grounding MCP server can do
The Claim Grounding MCP server is published by the GitHub account truepointmarketingpartners-dotcom. It has 5 tools. It can create or change data (5 tools: extract_claims, quick_check, verify_claim, check_answer and 1 more), but cannot delete data. None of its tools only reads.
5 tools bring in text other people can write (extract_claims, quick_check, verify_claim and 2 more).
The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 1.5.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 5Claude Code: ask
check_answerFact-check a whole answer: extracts every checkable claim and verifies each against Wikipedia, plus Wikidata structured facts for dates, numbers, quantities, ordinals and records.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.sources.items.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.sources.items.properties.url.description: "...teral hosts, custom ports and URLs with credentials are rejected (HTTP 400, not charged). W..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Check answer
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
deep_verifyUse when a claim is high-stakes, or when check_answer or extract_claims marks it unsure (their next_step gives the exact request).Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.sources.items.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.sources.items.properties.url.description: "...teral hosts, custom ports and URLs with credentials are rejected (HTTP 400, not charged). W..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Deep verify
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
extract_claimsSplit a text (for example an AI-generated answer) into atomic factual claims.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Extract claims
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
quick_checkFast, low-cost check of ONE factual claim.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Quick check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_claimCheck one factual claim against public Wikipedia sources and return a verdict (supported, contradicted, outdated, mixed or insufficient_evidence), a confidence score, a short reaso…Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.sources.items.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.sources.items.properties.url.description: "...teral hosts, custom ports and URLs with credentials are rejected (HTTP 400, not charged). W..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify claim
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://claim-grounding.prospectintel.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including extract_claims (write), quick_check (write), verify_claim (write), check_answer (write), deep_verify (write)
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 4 to 5
Findings
Matches of fixed checks, with the text they matched.
- Infoverify_claim
The input schema at properties.sources.items.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.sources.items.properties.url.description: "...teral hosts, custom ports and URLs with credentials are rejected (HTTP 400, not charged). W..."
- Infocheck_answer
The input schema at properties.sources.items.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.sources.items.properties.url.description: "...teral hosts, custom ports and URLs with credentials are rejected (HTTP 400, not charged). W..."
- Infodeep_verify
The input schema at properties.sources.items.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.sources.items.properties.url.description: "...teral hosts, custom ports and URLs with credentials are rejected (HTTP 400, not charged). W..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:quick_checkChanges things
- Changed:extract_claimsChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
- Tools that change things, listed without credentials: 4 to 5
Install
Pinned to version 1.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http claim-grounding https://claim-grounding.prospectintel.workers.dev/mcpclaude mcp add --transport http claim-grounding https://claim-grounding.prospectintel.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__claim-grounding__extract_claims",
"mcp__claim-grounding__quick_check",
"mcp__claim-grounding__verify_claim",
"mcp__claim-grounding__check_answer",
"mcp__claim-grounding__deep_verify"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as claim-grounding. Review it before you use it.
Capability tags behind 5 rules
- mcp__claim-grounding__extract_claims untrusted-input
- mcp__claim-grounding__quick_check untrusted-input
- mcp__claim-grounding__verify_claim untrusted-input
- mcp__claim-grounding__check_answer untrusted-input
- mcp__claim-grounding__deep_verify untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.truepointmarketingpartners-dotcom/claim-grounding/verify?hash=438d14589700c67e416e8b2dc9db4c33407934d9dce1801b3a4fba87ea4826fc" | jq -e '.changed == false'Pinned hash 438d14589700, from Nov 12, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.truepointmarketingpartners-dotcom/claim-grounding/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.truepointmarketingpartners-dotcom/claim-grounding)Source: MCP Registry · repository. Synced Nov 12, 2026, 20:18 UTC.
Claim Grounding MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Claim Grounding MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Claim Grounding MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Claim Grounding MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Claim Grounding MCP server have?
- 5 tools: 5 write. extract_claims, quick_check, verify_claim, check_answer and deep_verify.
Does the Claim Grounding MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Claim Grounding MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Claim Grounding MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.