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/raphy78626/screenshot-api/screenshot-api-mcpgit clone --depth 1 https://github.com/raphy78626/screenshot-apiWrote 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/raphy78626/screenshot-api/screenshot-api-mcp)<a href="https://agentmods.dev/mcp/raphy78626/screenshot-api/screenshot-api-mcp"><img src="https://agentmods.dev/badge/mcp/raphy78626/screenshot-api/screenshot-api-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
screenshot-api-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 3d 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
{ "screenshot-api-mcp": { "command": "npx", "args": [ "-y", "screenshot-api-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.
- 3d ago First seen · 9 lines scan A 0ca7193be8ab
screenshot-api-mcp is an MCP server published in the GitHub repository raphy78626/screenshot-api (0 stars, last pushed 27d 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
camoufox-playwright-mcp
The Playwright MCP, on Camoufox. Same tools, harder-to-detect browser. Runs locally from the camoufox-playwright-mcp Python package.
webshot-mcp
MCP server "webshot-mcp" as configured in Brandon-35/webshot-mcp. Runs locally from the webshot-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.
air-sdk
Collective intelligence for browser automation agents. Site capabilities, selectors, and extraction. Runs locally from the @arcede/air-sdk npm package. Needs 1 environment variable to run.
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.
browser-mcp
MCP server for browser-use. Runs locally from the browser-mcp Python package.