io.github.mgdsn/verify-api-mcp
This MCP server gives agents eight evidence-backed verification tools that return confirmed/contradicted/unknown verdicts with source URLs.
verify_citation— check whether a citation exists, is retracted, and whether title/authors/year/journal match canonical records (Crossref/OpenAlex).verify_url— check URL resolution, final status, redirects, Wayback Machine archive, and optional expected page content.verify_package— check npm/PyPI/crates.io package existence, deprecation/yank status, and known vulnerabilities (OSV.dev).verify_repo— check whether a GitHub repo exists and whether it is archived or disabled.verify_case— check whether a legal case citation exists and whether the case name matches the canonical record (CourtListener).verify_filing— check SEC EDGAR filing existence and whether form type/date match a CIK/accession claim.verify_drug— check FDA approval, NDC listing, or recall records and whether the given name matches (openFDA).verify_seller— check an x402 seller's existence, 402 challenge well-formedness, schema consistency, and whether its payout address is sanctioned.
Every response includes a verdict, individual checks, and evidence with source URLs; unknown is returned rather than guessing.
Provides tools for verifying GitHub repositories, including whether they exist and whether they are archived or disabled, via the GitHub REST API.
Provides tools for verifying npm packages, including existence, deprecation or yanked status, and known vulnerabilities, via the npm registry and OSV.dev.
Provides tools for verifying PyPI packages, including existence, deprecation or yanked status, and known vulnerabilities, via the PyPI registry and OSV.dev.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@io.github.mgdsn/verify-api-mcp Verify this citation: 'Doe et al. 2019, Science'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Verify API MCP Server
MCP server for Verify API: a pay-per-call verification service that gives agents a fast, structured, evidence-backed yes/no/unknown on claims they'd otherwise guess at.
Stop your agent from citing things that don't exist, installing things that shouldn't, or paying sellers that don't check out. Eight tools, one answer each, evidence attached.
Tools
verify_citation-- does a citation exist, is it retracted, and does the given title/authors/year/journal match the canonical record? Checked against Crossref (includes Retraction Watch data) with OpenAlex as a fallback.verify_url-- does a URL resolve, what's the final status and redirect chain, is it archived on the Wayback Machine, and (optionally) does expected text appear on the page?verify_package-- does an npm/PyPI/crates.io package exist, is it deprecated or yanked, and does it have known vulnerabilities? Checked against the registry plus OSV.dev advisories. Catches an agent installing a hallucinated or squatted package name.verify_repo-- does a GitHub repo exist, is it archived or disabled? Checked against the GitHub REST API. Catches an agent recommending or depending on a renamed, taken-down, or abandoned repo.verify_case-- does a legal case citation exist, and does the given case name match the canonical record? Checked against CourtListener. Catches a fabricated case citation, including a real-looking citation number paired with an invented case name. Existence only -- does not check whether a case is still good law.verify_filing-- given a filer's SEC CIK and a claimed accession number, does that filing exist, and does its form type/filing date match what's claimed? Checked against SEC EDGAR's submissions API. Catches a fabricated or misattributed filing citation, including a real-looking accession number paired with an invented form type or date.verify_drug-- given a claim_type (approval,ndc, orrecall) and its identifier, does that FDA record exist, and does the given name match the canonical record? Checked against openFDA. Catches a fabricated or misattributed drug approval, NDC listing, or recall citation. Existence/status only -- not medical advice.verify_seller-- before paying an x402 seller, does it exist and respond with a well-formed 402 challenge, is its own declared input/output schema internally consistent, and is its payout address sanctioned? Checked live against the seller itself plus a sanctions oracle and on-chain wallet history (Base payTo addresses only). Confirms the checkable things check out -- not a guarantee of trustworthiness.
Every response includes a verdict (confirmed / contradicted / unknown),
the individual checks that were run, and evidence with source URLs so a
human can verify the answer themselves. unknown is a valid, honest answer --
this server never guesses to avoid it.
Related MCP server: verification-mcp
Install
pip install verify-api-mcpConfigure
The primary way to use Verify API is x402 pay-per-call
(no key, no account, from $0.005/call -- $0.01 for verify_case) -- but this
MCP server specifically needs a subscription key instead, since x402 requires
a wallet most MCP clients don't have. Get one by subscribing to a plan at
goodsong.dev/#pricing (Solo, $15/mo, or Team,
$49/mo) -- the key is issued immediately on the checkout success page. There's
no free tier.
Then add your key to your MCP client's config (e.g. mcp.json):
{
"mcpServers": {
"verify-api": {
"command": "verify-api-mcp",
"env": {
"VERIFY_API_KEY": "vk_..."
}
}
}
}VERIFY_API_URL defaults to https://goodsong.dev and only needs to be set if
you're pointing at a different deployment.
License
MIT
Available Tools
2 toolsverify_citationA
Verify a citation: does it exist, is it retracted, and do the given title/authors/year/journal match the canonical record? Checked against Crossref (includes Retraction Watch data) with OpenAlex as a fallback when no DOI is given. Provide a doi and/or a title.
Inputs: doi, year, title, authors, +1 more.
verify_urlB
Verify a URL: does it resolve, what's the final status and redirect chain, is it archived on the Wayback Machine, and (optionally) does expected text appear on the page. Checked via direct fetch and the Internet Archive.
Inputs: url (required), expected_date, expected_content.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools target entirely different objects: one verifies bibliographic citations and the other verifies URLs. There is no overlap or ambiguity about which tool to select for a given task.
Both tools follow the exact same verb_noun snake_case pattern: verify_citation and verify_url. The naming is perfectly consistent and immediately communicates each tool's purpose.
Two tools is on the thin side for a server with the general purpose of 'verify'. However, each tool covers a distinct and meaningful verification type, so the count feels borderline rather than wasteful.
The citation tool covers existence, retraction status, and metadata matching, while the URL tool covers resolution, redirects, archive availability, and expected content. Together they provide thorough coverage of the stated verification domain with no obvious dead ends.
Related MCP Connectors
Real-time fact-check, citation verification, and source-freshness for AI agents.
Verify before you cite: URL checks, quotes, page-to-Markdown, metadata, schema, links, archives.
111Verifies legal citations vs primary sources: existence, quote match, proposition support.
Verify legal citations, case treatment, quotes and whole briefs against 10.7M U.S. opinions
Related MCP Servers
AlicenseNot gradedqualityNot gradedmaintenanceEnables fact-checking of AI responses against reliable sources and validation of responses against document content to ensure accuracy and reliability.-- AlicenseNot gradedqualityDmaintenanceEnables AI agents to fact-check claims, verify citations, and check source freshness using Wikipedia, Wikidata, Crossref, and Wayback Machine.1MIT
- AlicenseAqualityCmaintenanceVerifies factual claims against live sources and returns a verdict, confidence score, and citations for any agent to use before stating uncertain facts.61MIT
- AlicenseNot gradedqualityDmaintenanceEnables per-claim citation verification for AI-generated text by fetching cited sources and judging whether they support the claim, with verdicts and evidence quotes.50 npmMIT