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/bch1212/agentfetch-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/bch1212/agentfetch-mcp/agentfetch)<a href="https://agentmods.dev/mcp/bch1212/agentfetch-mcp/agentfetch"><img src="https://agentmods.dev/badge/mcp/bch1212/agentfetch-mcp/agentfetch/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/bch1212/agentfetch-mcp/agentfetch"><img src="https://agentmods.dev/badge/mcp/bch1212/agentfetch-mcp/agentfetch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentfetch 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 1mo 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
{
"agentfetch": {
"command": "uvx",
"args": [
"agentfetch-mcp"
],
"env": {
"JINA_API_KEY": "",
"FIRECRAWL_API_KEY": "",
"REDIS_URL": ""
}
}
}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.
- 1mo ago First seen · 13 lines scan A 3e8124ffbd2c
agentfetch is an MCP server published in the GitHub repository bch1212/agentfetch-mcp (3 stars, last pushed 4mo 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
mintlify-docs
MCP server "mintlify-docs", hosted remotely at www.mintlify.com, as configured in nottelabs/notte.
notte-docs
MCP server "notte-docs", hosted remotely at docs.notte.cc, as configured in nottelabs/notte.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
tools
MCP server "tools" as configured in aden-hive/hive. Runs aden_tools.mcp_server with python.
web-fetch
MCP server for fetching web content using Playwright browser. Runs locally from the fetcher-mcp npm package.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.