mcp server
OpenWarrant — Reference Verification
Fact-check citations: resolve, match, support claims; math rechecked. No API key — URL in.
Description as published by the maintainer. Source
- version 0.1.2
- active
active — Registry entry last updated 2026-07-23.
What this server can do
1 function, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
verify_references(url, deep, text, filename, bytes_b64)- Fact-check a document's REFERENCES and CLAIMS — built for AI-generated reports whose citations must be checked before they're trusted. USE THIS WHEN someone shares a report, article, whitepaper, or deep-research export (or a link to one) and asks: is this accurate / legit? are these citations real? fact-check this. did the AI make this up? Also use it proactively before relying on any AI-written document. Provide the document ONE way: `url` (a public http(s) link to a PDF or web page — fetched server-side, the cheapest call: no need to download or encode anything), `text` (pasted markdown/plain prose), OR `bytes_b64` (a base64 PDF; URLs are read from the PDF's link annotations, so they're exact). Default (fast): provenance (is it a ChatGPT deep-research export?), citation resolution (live / archived / dead, papers matched against arXiv/Crossref to catch 'real ID, wrong paper'), and internal MATH (recompute the doc's own arithmetic). Set `deep=true` to also fetch each cited source and judge whether it SUPPORTS or CONTRADICTS the claim (slower, ~a minute). Returns a trust summary, per-item tables, and a shareable `permalink` to the public fact-check record. HONEST BOUNDARY: this reports verification COVERAGE, not truth — 'supported' means evidence-backed (not necessarily true) and 'unsupported' means no evidence found (not necessarily false). It tells a reviewer WHERE to look; it does not bless the document, and it never affects the fraud risk band.
Last successful function declaration observed on . Source: https://www.stipple.sh/mcp-verify. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.stipple.sh/mcp-verify.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-23 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-23 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 1 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.stipple.sh | |
| mcp endpoint status | ok | The server listed 1 function when asked. | as of probe | www.stipple.sh |
Where to get it
Also from sketchjar
-
OpenWarrant — Document Verification Suite
Document forensics: tamper/AI checks, extract, identity, PII, adverse media. No API key needed.
-
OpenWarrant — AI Text Detection
Probability prose is AI-written, with the tells behind the score. No API key — text or URL in.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json