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.
npx agentmods add mcp/joshuaswarren/remnic/plugin-claude-code-remnicgit clone --depth 1 https://github.com/joshuaswarren/remnicWrote 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/joshuaswarren/remnic/plugin-claude-code-remnic)<a href="https://agentmods.dev/mcp/joshuaswarren/remnic/plugin-claude-code-remnic"><img src="https://agentmods.dev/badge/mcp/joshuaswarren/remnic/plugin-claude-code-remnic.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
remnic 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 5d 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
{
"remnic": {
"type": "http",
"url": "http://localhost:4318/mcp",
"headers": {
"Authorization": "Bearer {{REMNIC_TOKEN}}",
"X-Engram-Client-Id": "claude-code"
}
}
}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.
- 5d ago First seen · 10 lines scan A 28100cc37084
remnic is an MCP server published in the GitHub repository joshuaswarren/remnic (193 stars, last pushed yesterday), 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
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
brainlayer
MCP server "brainlayer" as configured in EtanHey/brainlayer. Launched with brainlayer-mcp-stdio-bridge.
palace-rs
MCP server "palace-rs" as configured in AncientiCe/palace-rs. Launched with https://github.com/AncientiCe/palace-rs/releases/download/v0.9.1/palace-0.9.1.mc.
claudedesktop-warnerco-schematica
MCP server "claudedesktop-warnerco-schematica" as configured in timothywarner-org/context-engineering. Runs locally from the warnerco-mcp Python package. Needs 1 environment variable to run.