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/studiomeyer-io/mcp-armorWrote 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/studiomeyer-io/mcp-armor/armor)<a href="https://agentmods.dev/mcp/studiomeyer-io/mcp-armor/armor"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/mcp-armor/armor/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/studiomeyer-io/mcp-armor/armor"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/mcp-armor/armor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
armor 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 23d 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
{
"armor": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/studiomeyer-io/mcp-armor:0.8.1"
],
"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.
- 23d ago Changed 448d48b2012c
- 1mo ago Changed 7832e70360ee
- 1mo ago First seen · 12 lines scan A 036be4a5fa8e
armor is an MCP server published in the GitHub repository studiomeyer-io/mcp-armor (1 stars, last pushed today), 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
academy
The Academy curriculum as an offline MCP library. Hosted course connector adds progress. Runs locally from the mcp-academy npm package. Needs 1 environment variable to run.
hook-conformance
Audits MCP servers for Claude Code mcptool hook readiness: idempotency, latency, side-effects. Runs locally from the mcp-hook-conformance npm package.
stdio-shellguard
Defense-in-depth for MCP stdio servers: shell-injection guard, AST audit CLI, RCE blocking. Runs locally from the mcp-stdio-shellguard npm package.
tenant-pair
Multi-user tenancy library for MCP servers. Pairs, groups, bi-temporal shared state, DSGVO erasure. Runs locally from the mcp-tenant-pair-demo npm package.
bft-progress-council-mcp
BFT Progress Council MCP — 5-voter Byzantine council halts agentic loops when no real progress is happening. Stops tokens bleeding on infinite spins. By MEOK AI Labs. Runs locally from the bft-progress-council-mcp Python package.
mcp-trustlayer
MCP server "mcp-trustlayer" as configured in neelbarm/mcp-trustlayer. Runs locally from the mcp-trustlayer Python package.