Check links live: broken, soft 404, redirects, missing anchors. Check a quote is really on a page.
Scored across 2 tools
The two tools address clearly different questions: link liveness/redirect status versus quote fidelity against a fetched page. Their trigger signals ('broken link', '404' vs. 'does this article actually say', 'verify this quote') do not overlap, so an agent can pick correctly without hesitation.
Both tools follow the same vouch_<verb>_<noun> snake_case pattern (vouch_check_links, vouch_check_quote). The shared prefix groups them as one family and the verbs/nouns are unambiguous.
Two tools is a thin surface even for a narrowly scoped verification server; there is no general 'fetch/inspect page' companion tool that would make the pair feel complete. The count is not wrong for the purpose, but it sits at the borderline of 'too few'.
The core lifecycle of sourcing — verifying a URL resolves and verifying a quote matches its cited page — is covered with rich status/verdict detail. Minor gaps remain: no support for verifying paraphrased claims, statistics without verbatim quotes, or multi-page source bundles, but agents can work around these.
Use when the user asks whether links work, or before links, sources or doc URLs go into an answer, README, report, email or code comment (signals: "are these links dead", "check the links in this README", "does this URL exist", "404", "broken link", "where does this redirect", "is this docs page still there"). Fetches each URL live (GET, redirects followed hop by hop) and returns per link a status: ok, redirected (link the final_url), soft_404 (answers 200 but the title says not found, or a deep link lands on the front page), anchor_missing (the #section id is not on the page), broken (404, 410 or other 4xx), server_error (5xx), blocked (401, 403, 429 or a bot challenge: not proof the page is missing), unreachable (DNS, connection or timeout) or invalid. Each result has http_status, every hop, final_url, page title and canonical; for broken pages it lists the closest real pages from the site's own sitemap (suggestions, the top one re-checked). Give urls (up to 15) or text (Markdown, HTML or plain text; its http and https links are extracted, first 15 checked). Example: {"urls":["https://docs.stripe.com/api/charge","https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#attributes"]}. Limits: a page can work in a browser and still be blocked here; pages built by JavaScript may hide anchors; one call makes at most 45 requests.
Inputs: text, urls, suggest.
Use when a quote, a statistic or a claim is attributed to a web page and the user asks whether the source says it, or before a citation goes into an answer, report, article or essay (signals: "does this article actually say", "verify this quote", "is this citation real", "check the source", "did they really write that", "fact-check this quote against the link"). Fetches the page once, extracts its visible text and returns per quote a verdict: exact (word for word), normalized (same words in order; only punctuation, capitals, spacing or curly quotes differ), close (similarity 0.85 or more, wording differs), partial (0.5 to 0.85) or not_found, with the matching passage, surrounding context, the words that differ and numbers_differ when a number changed (for example 1914 in the quote, 1912 on the page). Quotes with "..." are checked part by part. Example: {"url":"https://en.wikipedia.org/wiki/Alan_Turing","quotes":["widely regarded as the father of theoretical computer science"]}. Limits: a match shows the words are on the page, not that the claim is true; pages built by JavaScript may have little text in their HTML; PDFs and paywalled or bot-blocked pages cannot be read; up to 10 quotes of 1000 characters, at least 3 words each.
Inputs: url (required), quotes (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Check many URLs at once: HTTP status, redirect chains and loops, so you see which links break.
Check one web page for broken links, redirect chains hop by hop and mixed content. Free, no key.
Crawl a site for broken links, 404s, dead images, redirect chains and slow pages, with sources
Find broken links on a website: crawls its pages and reports 404s, errors and redirect chains
Add one secure layer between your agents and this server.