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/ochtum/CaptureScreenMCPInstalling this writes the configuration, not the program: `CaptureScreenMcp` has to be on your PATH already, or the server will not start.
Wrote 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/ochtum/capturescreenmcp/capture-screen)<a href="https://agentmods.dev/mcp/ochtum/capturescreenmcp/capture-screen"><img src="https://agentmods.dev/badge/mcp/ochtum/capturescreenmcp/capture-screen/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/ochtum/capturescreenmcp/capture-screen"><img src="https://agentmods.dev/badge/mcp/ochtum/capturescreenmcp/capture-screen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
capture-screen 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 1mo 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
{
"capture-screen": {
"command": "CaptureScreenMcp",
"args": [],
"env": {
"CAPTURE_SCREEN_DEFAULT_DISPLAY": "",
"CAPTURE_SCREEN_OUTPUT_DIR": "",
"CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL": ""
}
}
}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.
- 1mo ago First seen · 11 lines scan A 89dcc749c74d
capture-screen is an MCP server published in the GitHub repository ochtum/CaptureScreenMCP (3 stars, last pushed 6mo 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
plonk
MCP server for Plonk, a native macOS toolbox for windows, workspaces, screenshots, OCR, measuring, keep-awake, pointer tools and voice. Runs locally from the plonk-mcp npm package.
plonk
Plonk gives agents local macOS tools for windows, workspaces, screenshots, OCR, and more. Runs locally from the plonk-mcp npm package.
site-shot
MCP server for Site-Shot — give Claude and other AI agents the ability to take website screenshots (real Chromium, full-page, country proxies, automatic ad & cookie-banner removal). Runs locally from the site-shot-mcp npm package. Needs 1 environment variable to run.
site-shot-mcp
Website screenshots for AI agents: full-page, country proxies, ad & cookie-banner removal. Runs locally from the site-shot-mcp npm package. Needs 1 environment variable to run.
vision-memory-mcp
MCP server "vision-memory-mcp" as configured in putervision/vision-memory-mcp. Launched with vision-memory-mcp run. Needs 1 environment variable to run.
state-memory-mcp
MCP server "state-memory-mcp" as configured in putervision/vision-memory-mcp. Launched with state-memory-mcp run. Needs 1 environment variable to run.