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/Eilodon/CALMWrote 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/eilodon/calm/calm-mcp)<a href="https://agentmods.dev/mcp/eilodon/calm/calm-mcp"><img src="https://agentmods.dev/badge/mcp/eilodon/calm/calm-mcp/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/eilodon/calm/calm-mcp"><img src="https://agentmods.dev/badge/mcp/eilodon/calm/calm-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
calm-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 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
{
"calm-mcp": {
"command": "npx",
"args": [
"-y",
"@eilodon/calm-mcp"
],
"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 · 10 lines scan A 08374f17c9b0
calm-mcp is an MCP server published in the GitHub repository Eilodon/CALM (17 stars, last pushed 3d 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-30.
Other mcp servers, from other repositories
codeindex
Self-contained, deterministic repo-indexing engine: walk + language detection + symbol/import extraction (tree-sitter AST with regex fallback) + import resolution + typed cross-file link-graph + analytics. Ships as a single zero-dependency engine.mjs that. Runs locally from the @maxgfr/codeindex npm package.
viberevert
Local MCP server for AI coding safety: risk checks, sessions, checkpoints, and fix prompts. Runs locally from the viberevert npm package.
euthynos
Euthynos — deterministic repository intelligence for AI coding agents (MCP server): exact source spans, call graphs, clone detection, honest evidence boundaries. Runs locally from the euthynos npm package.
meeba-brain
Ground-truth code graph for your codebase: exact callers, callees, symbols & dependencies. Remote server at meeba-context-mcp-469248886325.us-central1.run.app.
no_human
Autonomous AI software-delivery orchestrator driving the Claude Agent SDK on your own Claude credentials. Runs locally from the no-human Python package.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Launched with sqry-mcp --no-daemon. Needs 1 environment variable to run.