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/madezmedia/acmiWrote 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/madezmedia/acmi/acmi-mcp)<a href="https://agentmods.dev/mcp/madezmedia/acmi/acmi-mcp"><img src="https://agentmods.dev/badge/mcp/madezmedia/acmi/acmi-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/madezmedia/acmi/acmi-mcp"><img src="https://agentmods.dev/badge/mcp/madezmedia/acmi/acmi-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
acmi-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
{ "acmi-mcp": { "command": "npx", "args": [ "-y", "@madezmedia/acmi-mcp" ], "env": { "UPSTASH_REDIS_REST_URL": "", "UPSTASH_REDIS_REST_TOKEN": "" } } }
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 · 13 lines scan A ec8af5c07b94
acmi-mcp is an MCP server published in the GitHub repository madezmedia/acmi (3 stars, last pushed 4d 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
titen-memory
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1. Runs locally from the titen-memory npm package. Needs 2 environment variables to run.
aura
Email address, webhook, durable memory and zero-token waiting for agents. Paid in USDC via x402. Remote server at aura.rohnelt.dev.
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.
pensyve
Universal memory runtime for AI agents — episodic, semantic, and procedural memory. Remote server at mcp.pensyve.com.
portable-agent-memory
MCP server "portable-agent-memory" as configured in skywaller0/Portable-Agent-Memory. Runs locally from the portable-agent-memory Python package.
myco-brain
Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres. Runs locally from the @mycobrain/mcp-server npm package.