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/jayjpatel9717/caido-screenshotWrote 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/jayjpatel9717/caido-screenshot/caido-screenshot-mcp)<a href="https://agentmods.dev/mcp/jayjpatel9717/caido-screenshot/caido-screenshot-mcp"><img src="https://agentmods.dev/badge/mcp/jayjpatel9717/caido-screenshot/caido-screenshot-mcp/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/jayjpatel9717/caido-screenshot/caido-screenshot-mcp"><img src="https://agentmods.dev/badge/mcp/jayjpatel9717/caido-screenshot/caido-screenshot-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
caido-screenshot-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 10d 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
{ "caido-screenshot-mcp": { "command": "npx", "args": [ "-y", "caido-screenshot-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.
- 10d ago First seen · 9 lines scan A 5bc56ce1ee32
caido-screenshot-mcp is an MCP server published in the GitHub repository jayjpatel9717/caido-screenshot (0 stars, last pushed 19d 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
apex-bounty
MCP server "apex-bounty" as configured in nadirzhon/apex. Runs locally from the apex-bounty Python package.
burpsuite-mcp-bridge
MCP server "burpsuite-mcp-bridge" as configured in 6jeffr3y/burpsuite-mcp-bridge. Runs ./mcp-server/server.py with python3. Needs 1 environment variable to run.
cve-lookup-mcp
MCP server "cve-lookup-mcp" as configured in Aashish-32/cve-lookup-mcp. Runs locally from the cve-lookup-mcp Python package.
kali-mcp
MCP server "kali-mcp" as configured in xhj-cloud/kali-mcp. Runs locally from the kali-mcp Python package.
mcp-noctua
MCP server "mcp-noctua" as configured in NeveuGregor/mcp-noctua. Runs locally from the mcp-noctua Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.