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/pangtongya/hermes-mcp-serverWrote 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/pangtongya/hermes-mcp-server/hermes)<a href="https://agentmods.dev/mcp/pangtongya/hermes-mcp-server/hermes"><img src="https://agentmods.dev/badge/mcp/pangtongya/hermes-mcp-server/hermes/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/pangtongya/hermes-mcp-server/hermes"><img src="https://agentmods.dev/badge/mcp/pangtongya/hermes-mcp-server/hermes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hermes 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
{
"hermes": {
"command": "hermes-mcp",
"args": [
"--endpoint",
"http://localhost:8080"
],
"env": {
"HERMES_API_KEY": "your-api-key-here"
}
}
}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 3420bb6ea4ef
hermes is an MCP server published in the GitHub repository pangtongya/hermes-mcp-server (1 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
mockzilla-mcp
Mockzilla MCP server. Mock any OpenAPI spec locally with Claude, Cursor, or Gemini CLI. Runs locally from the @mockzilla/mcp npm package. Needs 3 environment variables to run.
multi-select-reorder-mcp
MCP server "multi-select-reorder-mcp", hosted remotely at 127.0.0.1, as configured in dhruv-anand-aintech/agent-rules-sync.
panelica-mcp
Manage a Panelica hosting panel in plain English - 404 scoped, HMAC-signed tools. Runs locally from the panelica-mcp npm package. Needs 3 environment variables to run.
windows-context-mcp
MCP server "windows-context-mcp" as configured in nandhakumar-murugan/windows-context-mcp. Runs locally from the windows-context-mcp npm package.
wingman
MCP server "wingman" as configured in adeoluwaadesina/wingman-mcp. Runs wingman with python.
imgui
MCP server "imgui" as configured in SaloQT/imgui-mcp. Runs locally from the ${CLAUDE_PROJECT_DIR} Python package.