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/sethbang/mcp-screenshot-serverWrote 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/sethbang/mcp-screenshot-server/screenshot-server)<a href="https://agentmods.dev/mcp/sethbang/mcp-screenshot-server/screenshot-server"><img src="https://agentmods.dev/badge/mcp/sethbang/mcp-screenshot-server/screenshot-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
screenshot-server 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 8d 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-server": {
"command": "npx",
"args": [
"-y",
"universal-screenshot-mcp"
],
"env": {}
}
}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.
- 8d ago First seen · 10 lines scan A c436f7830418
screenshot-server is an MCP server published in the GitHub repository sethbang/mcp-screenshot-server (30 stars, last pushed today), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
safari-mcp
Native Safari browser automation for AI agents — 80 tools, zero Chrome overhead. Runs locally from the safari-mcp npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm 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.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package.
mirroir
MCP server "mirroir" as configured in jfarcand/mirroir-mcp. Launched with ${workspaceFolder}/.build/release/mirroir-mcp --yolo.
charlotte
Renders web pages into structured, agent-readable representations using headless Chromium. Runs locally from the @ticktockbent/charlotte npm package.