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/labtoolsstudio/fetchmcpWrote 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/labtoolsstudio/fetchmcp/fetchmcp)<a href="https://agentmods.dev/mcp/labtoolsstudio/fetchmcp/fetchmcp"><img src="https://agentmods.dev/badge/mcp/labtoolsstudio/fetchmcp/fetchmcp/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/labtoolsstudio/fetchmcp/fetchmcp"><img src="https://agentmods.dev/badge/mcp/labtoolsstudio/fetchmcp/fetchmcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fetchmcp 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
{
"fetchmcp": {
"command": "npx",
"args": [
"-y",
"@labtoolsstudio/fetchmcp"
],
"env": {}
}
}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 · 10 lines scan A 5952280030ba
fetchmcp is an MCP server published in the GitHub repository labtoolsstudio/fetchmcp (0 stars, last pushed 2mo 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
web-fetch-mcp
Resilient web-fetch MCP server: 3-tier escalation (curlcffi -> Patchright -> nodriver) that fails honestly, with article-extraction mode and automatic content-type handling (HTML/JSON/PDF/image). Runs locally from the web-fetch-mcp Python package.
chrome-mcp-server
MCP server "chrome-mcp-server", hosted remotely at 127.0.0.1, as configured in iloveitaly/llm-ide-rules.
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.
mcp-server
Web scraping MCP server — scrape, extract structured data, screenshot any site with anti-bot bypass. Runs locally from the alterlab-mcp-server npm package.
page2ai-mcp
Convert web pages or HTML to clean Markdown for LLM context. Local, no external API calls. Runs locally from the @page2ai/mcp npm package.
scraper
Web scraping MCP — extract clean markdown, links, and metadata from any URL. Runs locally from the mcp-server-scraper npm package.