Citation Check
Server Details
Does a cited URL exist, and does the source name what your claim names? Two answers.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: check_citation performs the actual verification, while verdict_meanings explains the interpretation of results. There is no overlap or ambiguity in their purposes.
Both names use snake_case, which is consistent, but check_citation follows a verb_noun pattern while verdict_meanings is a noun phrase, creating a slight semantic inconsistency. However, with only two tools, the names are still predictable and descriptive.
With only two tools, the server feels minimal and is borderline according to the calibration. The narrow focus on citation checking justifies the small count, but it is still on the thin side for a tool set.
The core workflow of checking a citation is fully covered by check_citation, and verdict_meanings fills the need for understanding statuses and relevance values. There are no obvious gaps for the server's stated purpose, though it is intentionally minimal.
Available Tools
2 toolscheck_citationCheck whether a citation holds upARead-onlyInspect
Fetch a URL and report whether it exists, and whether the source names the same entity as the claim you attach to it. These are two different questions and conflating them is the failure this exists to catch: a URL can return 200 and describe a different gene entirely. No account needed, nothing is stored about you.
Inputs: url (required), claim.
verdict_meaningsWhat the verdicts mean, and what they do notARead-onlyInspect
The exact semantics of every status and relevance value, including what this checker cannot determine. Read once before trusting a verdict.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Fact-check claims against live web sources: verbatim evidence, coherence-gated verdict.
Check whether a page URL supports a claim.
Verify whether a supplied public source currently supports one atomic factual claim.
Verify cited URLs still resolve: reachability, HTTP status and page title. x402-paid.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceVerifies claims with verdicts (supported/disputed/unverifiable), confidence scores, and cited sources by cross-referencing FoundryNet Data Network and web search.MIT
- AlicenseAqualityBmaintenanceEnables agents to verify whether citations exist and match canonical records, and whether URLs resolve and contain expected content, with evidence-backed confirmed, contradicted, or unknown verdicts.245 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables fetching a cited source and confirming that a quoted sentence actually appears there verbatim across multiple independent retrieval paths, returning SUPPORTED, CONTRADICTED, or UNVERIFIABLE verdicts along with any numbers in the claim the source doesn't contain. It leaves the judgment of whether the sentence backs the claim to the writer, checking only that the relied-upon text exists where it is said to.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceURL reality check for AI agents — returns HTTP status, SHA-256 content hash, classification, readability score, title, and wayback-machine fallback when dead, cached 10 minutes at $0.001 per call.-
Glama MCP Gateway
Add one secure layer between your agents and this server.