Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/infinit3labs/web-research-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/infinit3labs/web-research-mcp/deep-web-research-mcp)<a href="https://agentmods.dev/mcp/infinit3labs/web-research-mcp/deep-web-research-mcp"><img src="https://agentmods.dev/badge/mcp/infinit3labs/web-research-mcp/deep-web-research-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/infinit3labs/web-research-mcp/deep-web-research-mcp"><img src="https://agentmods.dev/badge/mcp/infinit3labs/web-research-mcp/deep-web-research-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deep-web-research-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "deep-web-research-mcp": { "command": "uvx", "args": [ "deep-web-research-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 8 lines scan A d8af7ad051ca
deep-web-research-mcp is an MCP server published in the GitHub repository infinit3labs/web-research-mcp (0 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
arxiv-mcp-server
Search arXiv, fetch paper metadata, and read full-text content. Runs locally from the @cyanheads/arxiv-mcp-server npm package. Needs 5 environment variables to run.
web-search
Live web search and clean-markdown page fetch over the Keenable web index. Runs locally from the @keenable/mcp npm package. Needs 1 environment variable to run.
openai-responses-mcp
Lightweight MCP server (Responses API core). OpenAI integration + websearch. Runs locally from the openai-responses-mcp npm package.
openresearch-mcp
Zero-auth cross-domain research MCP server — web, academic, GitHub, news, weather, macro/finance, SEC, biomedical, Bluesky, YouTube, and more. Runs locally from the openresearch-mcp Python package. Needs 4 environment variables to run.
mcp-serp
MCP Server for Google SERP Search via AceDataCloud API. Runs locally from the mcp-serp Python package. Needs 1 environment variable to run.
hn-tech-signal-mcp
MCP server for tech & AI intelligence – aggregates HackerNews, arXiv, Lobste.rs and GitHub. No API key required. Runs locally from the hn-tech-signal-mcp Python package.