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/azixxxxx/HydraWrote 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/azixxxxx/hydra/hydra-hydra)<a href="https://agentmods.dev/mcp/azixxxxx/hydra/hydra-hydra"><img src="https://agentmods.dev/badge/mcp/azixxxxx/hydra/hydra-hydra/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/azixxxxx/hydra/hydra-hydra"><img src="https://agentmods.dev/badge/mcp/azixxxxx/hydra/hydra-hydra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hydra 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
{
"hydra": {
"command": "node",
"args": [
"./dist/server.js"
],
"cwd": "."
}
}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 · 9 lines scan A 267e25ea55c8
hydra is an MCP server published in the GitHub repository azixxxxx/Hydra (0 stars, last pushed 5d 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
claudexor
MCP server "claudexor" as configured in razzant/claudexor. Launched with claudexor mcp serve.
claudexor
Route coding work across Claude Code, Codex, Cursor, and OpenCode with shared context. Runs locally from the claudexor 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.
mochi
MCP server "mochi", hosted remotely at mochi.fast, as configured in khromov/codebay.
apple-docs
MCP server "apple-docs", hosted remotely at 127.0.0.1, as configured in sane-apps/SaneProcess.
macos-automator
MCP server "macos-automator", hosted remotely at 127.0.0.1, as configured in sane-apps/SaneProcess.