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/ashlrai/webfetchWrote 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/ashlrai/webfetch/mcp-webfetch)<a href="https://agentmods.dev/mcp/ashlrai/webfetch/mcp-webfetch"><img src="https://agentmods.dev/badge/mcp/ashlrai/webfetch/mcp-webfetch/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/ashlrai/webfetch/mcp-webfetch"><img src="https://agentmods.dev/badge/mcp/ashlrai/webfetch/mcp-webfetch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
webfetch 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
{
"webfetch": {
"command": "npx",
"args": [
"-y",
"getwebfetch-mcp"
],
"env": {
"UNSPLASH_ACCESS_KEY": "",
"PEXELS_API_KEY": "",
"PIXABAY_API_KEY": "",
"BRAVE_API_KEY": "",
"SERPAPI_KEY": ""
}
}
}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 · 16 lines scan A f85ecadeae85
webfetch is an MCP server published in the GitHub repository ashlrai/webfetch (3 stars, last pushed 8d 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
titen-memory
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1. Runs locally from the titen-memory npm package. Needs 2 environment variables to run.
cyanheads-mcp-server
Fleet discovery for the cyanheads MCP ecosystem — semantic search + install snippets. Runs locally from the @cyanheads/cyanheads-mcp-server npm package. Needs 6 environment variables to run.
usda-mcp-server
Search foods, compare nutrients, and look up the full USDA FoodData Central database. Runs locally from the @cyanheads/usda-mcp-server npm package. Needs 2 environment variables to run.
mcp-session-bridge
Drive a browser you are already signed into, through the free T3rnel Browser extension. Runs locally from the @t3ratech/mcp-session-bridge npm package. Needs 3 environment variables to run.
swarm-mcp
A Model Context Protocol (MCP) server implementation that uses Ethereum Swarm's Bee API for storing and retrieving data. Runs locally from the swarm-mcp npm package.
mcp
Read any web page as clean Markdown for AI agents: fetch, search, metadata, links. SSRF-safe. Remote server at mcp.vanshul.com.