Provenancewhere it came from, and what was verified
Published by the owner of studiomeyer.io, who proved control of the domain through the official MCP registry.
🛡 Permissions & trustwhat this server can touch before you run it
No permission details are published for this server yet. Check the source before you run it.
About
Security sidecar for MCP servers: prompt-injection scan, Ed25519 verify, tools/list drift. 10 tools.
Packages & transports
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
Raise this grade
up to +9 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Already earned (5) ▾Already earned (5) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.studiomeyer/armor)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"armor": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/studiomeyer-io/mcp-armor:0.7.0"
]
}
}
}▶ Try itrun it locally
This is a local server, so it runs on your machine, not ours. Paste this to open it in the official MCP Inspector and poke at its tools:
npx @modelcontextprotocol/inspector docker run -i --rm ghcr.io/studiomeyer-io/mcp-armor:0.7.0