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.
npx agentmods add mcp/mlawsonking/mcp/web-tools-mcpgit clone --depth 1 https://github.com/mlawsonking/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/mlawsonking/mcp/web-tools-mcp)<a href="https://agentmods.dev/mcp/mlawsonking/mcp/web-tools-mcp"><img src="https://agentmods.dev/badge/mcp/mlawsonking/mcp/web-tools-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
web-tools-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 5d 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
{
"web-tools-mcp": {
"command": "npx",
"args": [
"-y",
"web-tools-mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 5d ago First seen · 10 lines scan A 9b8519c4c3de
web-tools-mcp is an MCP server published in the GitHub repository mlawsonking/MCP (0 stars, last pushed today), 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
upapi-mcp
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more. Runs locally from the @upapi/mcp npm package. Needs 1 environment variable to run.
scraper-api-mcp
Model Context Protocol (stdio) server exposing every scraper-api.com endpoint as a tool. Runs locally from the scraper-api-mcp npm package.
agentlock-browser
Provenance-gated browsing tools for AI agents, over MCP. AgentLock enforces which channel a value came from before the browser acts on it. Runs locally from the agentlock-browser Python package.
mcp-server-screenshot
Pixel-perfect website screenshot service exposed as both REST API and MCP server. Runs locally from the mcp-server-screenshot Python package.
stdio-full
MCP server "stdio-full" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
skyvern
AI-powered browser automation — navigate, click, fill forms, and extract data from any website. Remote server at api.skyvern.com.