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/Koreahwan/wraith-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/koreahwan/wraith-mcp/wraith-mcp)<a href="https://agentmods.dev/mcp/koreahwan/wraith-mcp/wraith-mcp"><img src="https://agentmods.dev/badge/mcp/koreahwan/wraith-mcp/wraith-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
wraith-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 7d 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
{ "wraith-mcp": { "command": "uvx", "args": [ "wraith-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.
- 7d ago First seen · 8 lines scan A e0f6bca72d46
wraith-mcp is an MCP server published in the GitHub repository Koreahwan/wraith-mcp (0 stars, last pushed 3mo 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
browser-use
Make websites accessible for AI agents. Runs locally from the browser-use Python package.
safari-mcp
Native Safari browser automation for AI agents — 80 tools, zero Chrome overhead. Runs locally from the safari-mcp npm package.
browser-mcp
MCP server "browser-mcp" as configured in EndymionLee/PilotBrowseMCP. Runs BrowserPlugin\server\dist\index.js with node.
tidesurf
MCP server "tidesurf" as configured in TideSurf/core. Launched with bun src/cli.ts mcp.
helmdeck
Self-hosted MCP server: sandboxed browser, desktop, vision, code-edit packs for any agent. Runs locally from the @helmdeck/mcp-bridge npm package. Needs 2 environment variables to run.
chrome-bridge
Your real, logged-in Chrome as an MCP server: 60 token-efficient web-dev tools. ChromeOS included. Runs locally from the chrome-bridge-mcp npm package.