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/cybort360/cairnWrote 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/cybort360/cairn/cairn-mcp)<a href="https://agentmods.dev/mcp/cybort360/cairn/cairn-mcp"><img src="https://agentmods.dev/badge/mcp/cybort360/cairn/cairn-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/cybort360/cairn/cairn-mcp"><img src="https://agentmods.dev/badge/mcp/cybort360/cairn/cairn-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cairn-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 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
{
"cairn-mcp": {
"command": "uvx",
"args": [
"cairn-mcp"
],
"env": {
"CAIRN_TOKEN": "",
"CAIRN_API_URL": "https://cairn-octanes-projects.vercel.app"
}
}
}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 3bcb2b42e1a9
cairn-mcp is an MCP server published in the GitHub repository cybort360/cairn (0 stars, last pushed 2mo 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
engram
Persistent storage for local modules. Runs locally from the engram npm package.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
tokenmizer
MCP server "tokenmizer" as configured in Shweta-Mishra-ai/tokenmizer. Runs tokenmizer.mcp.server with python3. Needs 2 environment variables to run.
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.
todox
Memory for coding agents: the decisions, the dead ends, and where the last session stopped. Remote server at www.todox.dev.
bitatlas
Zero-knowledge encrypted storage for humans and AI agents. Client-side AES-256-GCM, EU-hosted. Runs locally from the @bitatlas/mcp-server npm package. Needs 4 environment variables to run.