A
licenseA
qualityB
maintenanceVerifies factual claims against live sources and returns a verdict, confidence score, and citations for any agent to use before stating uncertain facts.
6
MIT
Fact Verification MCP
Server Details
Verify claims with verdict, confidence & cited sources; batch verify, source checks, daily brief.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- FoundryNet/fact-check-mcp
- GitHub Stars
- 0
- Server Listing
- Fact Check MCP
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
5 tool updates
- Changed
batch_verify1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
brief_summary1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
daily_brief1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402 (x402 rail)."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
source_check1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
- Changed
verify_claim1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction signature, when re-calling after a 402."
1 tool update
- Added
brief_summary
1 tool update
- Changed
daily_brief2 fields changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"Solana tx signature, when re-calling after a 402 (x402 rail)." - added
Input schema / properties / stripe_tokenAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header." +}
5 tool updates
- First observed
batch_verify - First observed
daily_brief - First observed
mint_info - First observed
source_check - First observed
verify_claim
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Fact-check claims against independent sources — fast verdict or deep multi-step investigation.
Independent fact-checking for AI answers: a verdict and sources for every claim.
Check claims against a fact-store: consistent, contradicts, or unverifiable — with a receipt.
Verify citations in AI text: fetches each cited source, returns verdicts with evidence quotes.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables per-claim citation verification for AI-generated text by fetching cited sources and judging whether they support the claim, with verdicts and evidence quotes.102MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to verify their own output mid-task by checking every claim against provided sources, returning supported, partial, unsupported, or contradicted verdicts with exact citations.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to verify claims with evidence-based truth scores and confidence levels by running a deterministic pipeline of evidence lanes and adversarial checks.22MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.5/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: batch and single claim verification, source credibility check, daily briefs (full and summary), and network info. No overlapping functionality.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern (e.g., verify_claim, batch_verify, source_check). The convention is uniform and descriptive.
Tool Count5/5
With 6 tools, the set is well-scoped for a fact verification server. Each tool serves a necessary function without redundancy or bloat.
Completeness4/5
The tool set covers core verification workflows: single and batch claims, source credibility, daily briefs, and network info. A minor gap is the lack of a tool to retrieve historical or cached claims individually, but overall it's thorough.