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/usewrit/writ-mcpWrote 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/usewrit/writ-mcp/writ-cloud)<a href="https://agentmods.dev/mcp/usewrit/writ-mcp/writ-cloud"><img src="https://agentmods.dev/badge/mcp/usewrit/writ-mcp/writ-cloud/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/usewrit/writ-mcp/writ-cloud"><img src="https://agentmods.dev/badge/mcp/usewrit/writ-mcp/writ-cloud.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
writ-cloud 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
{ "writ-cloud": { "command": "npx", "args": [ "-y", "writ-mcp" ], "env": { "WRIT_API_KEY": "" } } }
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 · 12 lines scan A 91ffc9813083
writ-cloud is an MCP server published in the GitHub repository usewrit/writ-mcp (1 stars, last pushed 9d 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-10-11.
Other mcp servers, from other repositories
arachne-mcp
🕷️ MCP server for Arachne — search, scrape, browser, vision, transcribe, RAG, Social Research, GitHub (trending/PRs/activity) + VRT visual (Oito Olhos). Tool list fetched from the server registry. Runs locally from the arachne-mcp Python package. Needs 2 environment variables to run.
aethyn-browser-mcp
Local Playwright browser through residential proxies — agent picks country + sticky identity. Runs locally from the aethyn-browser-mcp npm package. Needs 3 environment variables to run.
safari-mcp
Native Safari browser automation for AI agents — 80 tools, zero Chrome overhead. Runs locally from the safari-mcp npm package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
real-browser
MCP server + Chrome extension for AI browser control with real sessions. Runs locally from the real-browser-mcp npm package.
ai-browser
MCP server "ai-browser" as configured in AI-XiaoDao/ai-browser-mcp. Runs CEFbro/AI-Fbowser-Mcp/mcp_bridge.js with node. Needs 3 environment variables to run.