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/ScreenifyStudio/screenify-mcpInstalling this writes the configuration, not the program: `https://github.com/ScreenifyStudio/screenify-mcp/releases/download/v2.2.1/screenify.mcpb` 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/screenifystudio/screenify-mcp/screenify)<a href="https://agentmods.dev/mcp/screenifystudio/screenify-mcp/screenify"><img src="https://agentmods.dev/badge/mcp/screenifystudio/screenify-mcp/screenify/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/screenifystudio/screenify-mcp/screenify"><img src="https://agentmods.dev/badge/mcp/screenifystudio/screenify-mcp/screenify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
screenify 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
{ "screenify": { "command": "https://github.com/ScreenifyStudio/screenify-mcp/releases/download/v2.2.1/screenify.mcpb", "args": [], "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.
- 1mo ago First seen · 7 lines scan A fc64c5633fe5
screenify is an MCP server published in the GitHub repository ScreenifyStudio/screenify-mcp (0 stars, last pushed 22d 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
codex-mcp-bridge
MCP server "codex-mcp-bridge", hosted remotely at codex-mcp-bridge.buidangminh23.chatgpt.site, as configured in buidangminh23/codex-mcp-bridge.
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.
rail-connector-mcp
MCP server "rail-connector-mcp" as configured in SNComrade/Rail-Connector-MCP. Runs locally from the rail-connector-mcp npm package.
mint
Inspect Mac and AI-tool storage, explain file activity, and clean safely with Trash and Undo. Runs locally from the @dzg-studio/mcp-server-mint npm package.
truepath-pdf-mcp
Local-only PDF tools for AI — extract text, search, split/merge, render pages. Files never leave. Runs locally from the @truepathpdf/mcp-server npm package.