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/reeinharddd/snapmcp/snapmcpgit clone --depth 1 https://github.com/reeinharddd/snapmcpWrote 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/reeinharddd/snapmcp/snapmcp)<a href="https://agentmods.dev/mcp/reeinharddd/snapmcp/snapmcp"><img src="https://agentmods.dev/badge/mcp/reeinharddd/snapmcp/snapmcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
snapmcp 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
{
"snapmcp": {
"command": "npx",
"args": [
"-y",
"snapmcp"
],
"env": {
"SNAPMCP_DIR": "./captures",
"SNAPMCP_THEME": "",
"SNAPMCP_FORMAT": "png",
"SNAPMCP_QUALITY": "90",
"SNAPMCP_SHADOW": "none",
"SNAPMCP_ALLOWED_PATHS": "",
"SNAPMCP_SSRF_PROTECTION": "true",
"SNAPMCP_CHROME_EXECUTABLE": "",
"SNAPMCP_CHROME_PROFILE": ""
}
}
}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 · 20 lines scan A 6a738a54d706
snapmcp is an MCP server published in the GitHub repository reeinharddd/snapmcp (0 stars, last pushed 5d 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
deveyes
MCP server that gives AI coding assistants eyes to see visual output from local development environments. Runs locally from the deveyes npm package.
google-surf-mcp
Web, academic and code search with graph RAG, data lineage, ontology and cross-project schema links. Runs locally from the google-surf-mcp npm package. Needs 19 environment variables to run.
plonk
MCP server for Plonk, a macOS window manager: zones you draw yourself, workspaces, keep-awake, screenshots and on-device OCR, as tools an agent can call. Runs locally from the plonk-mcp npm package.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
freetaxusa-mcp
MCP server "freetaxusa-mcp" as configured in schwarztim/freetaxusa-mcp. Runs locally from the freetaxusa-mcp npm package.
invisible-playwright-mcp
Stealth Firefox browser as an MCP server for AI agents. Runs locally from the invisible-playwright-mcp Python package.