The web-researcher MCP server is an open-source tool that connects AI assistants—such as Claude, GPT, and any other MCP-compatible system—to a comprehensive set of research capabilities designed around provenance, not just relevance. Rather than accepting whatever the web returns, this MCP server treats every source as suspect until proven otherwise, offering a robust defense against sloptimization and AI citation rot. Its core value is providing honest, verifiable evidence so that AI recommendations are based on real sources that actually support the claims made. This is the tool for anyone who needs trustworthy AI research in an era of manipulated web content.
The concrete problem it solves is the pervasive issue of sloptimization, where companies flood the web with self-serving listicles, hidden prompt injections, and sock-puppet campaigns designed not to convince humans but to train chatbots. AI search tools, relying on semantic relevance rather than traditional ranking signals, cannot distinguish between a genuine review and a company's own marketing copy. This leads to false confidence in AI-generated answers, as chatbots cite decorative sources that do not say what they claim. Stanford Law Review documented AI-fabricated citations in legal filings, and Columbia Journalism Review found over 60% of news articles contain miscited sources. Web Researcher MCP directly addresses this by providing tools that check whether a citation exists, is retracted, still resolves, and actually supports the claim.
The first major feature group is the verify_recommendation tool, built specifically to detect when a source ranks itself first in a list of recommendations. It checks four signals in parallel: self-promotion by comparing the source domain to the brand it recommends, conflict of interest by scanning author bios for employment or funding relationships, domain reputation against a curated dataset, and link liveness by checking HTTP status. The output is an array of flags such as "self_promotion" or "conflict_of_interest" that provide evidence without rendering a verdict. This is extremely useful when evaluating product comparisons or vendor lists, because it exposes when a company's own blog touting itself as the best is cited as an independent source. The tool uses a deliberate lexical check that catches brand name matches, and the limitation of missing subsidiary relationships is documented and planned for expansion.
The second major feature group is verify_citation, designed specifically for the citation rot epidemic. Given a DOI, URL, or free-text reference, it runs three parallel checks: whether the source exists by querying Crossref and OpenAlex, whether it has been retracted by checking the Retraction Watch database, and whether the link still resolves live with a Wayback fallback for dead links. When a claim parameter is provided, the tool fetches the source and performs a lexical coverage check to see if the text actually addresses the assertion. For example, if a paper on quantum computing is cited as evidence that remote work increases productivity, the tool flags "mischaracterized" and returns evidence sentences. This is the exact failure mode appearing in legal sanctions and academic retractions, where real sources are cited for things they do not say. The tool never conflates "I can't verify this" with "this is fake", distinguishing not_found from unchecked.
admin
The third feature group is audit_bibliography, which runs the same verification checks across an entire reference list in a single call. It accepts CSL-JSON, RIS, or BibTeX documents, or an explicit list of references, and processes up to 200 entries concurrently. The output is a corpus summary showing counts for retracted, deadLink, notFound, unchecked, mischaracterized, and ok entries. This enables complete bibliography audits before filing a brief, submitting a paper, or publishing an article. Additionally, the lens system allows users to restrict searches to trusted domains like journalism, academic, government, and clinical, using site: operators so that GEO-optimized brand blogs cannot appear in results. Sixteen lens domains ship out of the box, making it straightforward to limit research to peer-reviewed journals or established news organizations. This prevents the broad, untargeted searches that sloptimized content exploits.
The overall approach of Web Researcher MCP is to provide a set of research tools that create an audit trail from initial search to final citation. It supports research sessions that record every URL visited, every search run, and every source scraped during a task, which can be exported in CSL-JSON, RIS, BibTeX, MLA, APA, or RIS format. This exported bibliography can then be passed to audit_bibliography for a complete trust audit before the research is used. The workflow is designed to be transparent: the AI assistant uses these tools explicitly, so the user sees the verification steps rather than trust a black-box synthesis. By connecting through the Model Context Protocol, the server works seamlessly with Claude, GPT, and other agents, providing over 25 research tools covering verification, citation auditing, academic search, legal records, economic data, and clinical trials.
A concrete use case is an executive evaluating project management software. When a chatbot recommends ClickUp first, citing three sources, the AI assistant using Web Researcher MCP runs verify_recommendation on the links. The first source returns selfPromotionSignal.detected: true because it's from clickup.com ranking ClickUp first. The second is clean, but the third has linkLive: false with a 404 status. The assistant then runs verify_citation with the claim from the surviving source and finds claimSupport: "not_addressed" — the article mentions ClickUp only in passing without supporting enterprise suitability. Finally, the assistant uses web_search with lens: "journalism" and "tech" to find independent reviews from PCMag, The Verge, and G2. The user receives a clear picture: the top source is self-promotional, one is dead, and the only surviving source doesn't back the claim, while independent reviews provide genuine comparisons.
The target users are researchers, journalists, lawyers, academics, and developers who rely on AI assistants for information retrieval and verification. It works with any MCP-compatible AI assistant including Claude Code, Claude Desktop, Cursor, and Zed. The server is free and open-source, installable in seconds with uvx web-researcher-mcp, and requires zero API keys for basic functionality (DuckDuckGo works out of the box, with optional Google/Brave configuration for broader coverage). It offers 25+ research tools covering verification, citation auditing, academic search, legal records, economic data, clinical trials, and more. The main takeaway is that Web Researcher MCP restores trust in AI-generated research by applying editorial and scientific verification standards at machine speed, ensuring that every citation is real, current, and actually supports the claim it is supposed to back.
Developers integrating AI assistants via MCP who need reliable source verification. Academic researchers and graduate students verifying citations in papers and theses. Journalists fact-checking sources for articles. Lawyers and legal professionals auditing citations in briefs and filings. Executives and procurement teams evaluating vendor claims. Data scientists curating training datasets. Editors and publishers ensuring citation integrity in published works.