mcp-armor
OCI · GHCR.IO/STUDIOMEYER-IO/MCP-ARMOR:0.8.0 · SCANNED SEP 20
Security sidecar for MCP servers: 11 read-only control-plane tools for prompt-injection checks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 683 tokens (~62/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 19% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the mcp-armor server?
mcp-armor runs locally as a container image, launched with docker run --rm -i ghcr.io/studiomeyer-io/mcp-armor:0.8.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/studiomeyer-io/mcp-armor:0.8.0
claude mcp add io-studiomeyer-armor -- docker run --rm -i ghcr.io/studiomeyer-io/mcp-armor:0.8.0
{
"mcpServers": {
"io-studiomeyer-armor": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/studiomeyer-io/mcp-armor:0.8.0"
]
}
}
} {
"servers": {
"io-studiomeyer-armor": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/studiomeyer-io/mcp-armor:0.8.0"
]
}
}
} codex mcp add io-studiomeyer-armor -- docker run --rm -i ghcr.io/studiomeyer-io/mcp-armor:0.8.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-studiomeyer-armor": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/studiomeyer-io/mcp-armor:0.8.0"
],
"enabled": true
}
}
} mcp_servers:
io-studiomeyer-armor:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/studiomeyer-io/mcp-armor:0.8.0"] {
"McpServers": {
"io-studiomeyer-armor": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/studiomeyer-io/mcp-armor:0.8.0"
]
}
}
} {
"mcpServers": {
"io-studiomeyer-armor": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/studiomeyer-io/mcp-armor:0.8.0"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 4 Sept 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/studiomeyer-io/mcp-armor:0.8.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
armor_check_cve ~42
Look up a server name in the curated CVE feed and return affected entries.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | yes | – |
| server_version | string | – | – |
No output schema declared.
No examples provided.
armor_get_drift_history ~119
v0.5 Layer 7 — Inspect the tools-list schema-drift baselines persisted by `mcp-armor wrap`. Read-only. Optional `program` arg narrows the report to one upstream; omit it to list every pinned baseline. Closes the Rug-Pull / Silent-Redefinition threat class (Invariant Labs, CyberArk Full-Schema Poisoning).
| Name | Type | Req | Description |
|---|---|---|---|
| program | string | – | When set, return the full per-tool fingerprint detail for one program. When omitted, return a summary list of every pinned baseline. |
No output schema declared.
No examples provided.
armor_get_keystore ~63
v0.2 — List pinned TOFU maintainer public keys (server_name + fingerprint + pinned_at_iso). Read-only inspection of the keystore configured at sidecar startup (no caller-supplied path — operator-only via `--keystore` flag).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
armor_get_policy ~27
Return the active policy: file path, rules, fail mode, scan flags, version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
armor_list_blocked ~37
Read recent blocked tool calls from the in-memory ring buffer.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since_iso | string | – | – |
No output schema declared.
No examples provided.
armor_rekor_lookup ~78
v0.2 — Query the Sigstore Rekor transparency log for inclusion of a manifest's artifact hash. Requires --features sigstore-bridge at build time. Network call.
| Name | Type | Req | Description |
|---|---|---|---|
| rekor_url | string | – | Override Rekor endpoint; defaults to https://rekor.sigstore.dev |
| tools_list_response | object | yes | – |
No output schema declared.
No examples provided.
armor_scan_payload ~33
Scan an arbitrary payload for prompt-injection patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | – |
| payload | string | yes | – |
No output schema declared.
No examples provided.
armor_scan_tools_list ~139
v0.8 Layer 8 — Scan a captured tools/list response for tool-description / full-schema poisoning (model-directed instructions hidden in tool descriptions, parameter schemas, enum values or defaults). Read-only; never spawns the upstream. Pass `tools_list` as the response object or a raw JSON string. Closes the first-sight Tool Poisoning (Invariant Labs) / Full-Schema Poisoning (CyberArk) / OWASP MCP03 class that Layer 7 drift (which only catches later changes) leaves open on the initial baseline.
| Name | Type | Req | Description |
|---|---|---|---|
| tools_list | – | yes | The tools/list response, as a JSON object or a JSON string. |
No output schema declared.
No examples provided.
armor_simulate_attack ~39
Run the static simulate_payload for a CVE through the scanner. Never spawns the upstream binary.
| Name | Type | Req | Description |
|---|---|---|---|
| cve_id | string | yes | – |
No output schema declared.
No examples provided.
armor_verify_bundle ~44
v0.2 — Parse a cosign sigstore.json bundle and structurally verify the Rekor SignedEntryTimestamp shape. Offline.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_json | string | yes | – |
No output schema declared.
No examples provided.
armor_verify_manifest ~62
Verify Ed25519 signature over canonical-JSON form of a tools/list response.
| Name | Type | Req | Description |
|---|---|---|---|
| public_key_b64 | string | yes | – |
| signature_b64 | string | yes | – |
| signed_at_iso | string | – | – |
| tools_list_response | object | yes | – |
No output schema declared.
No examples provided.
What is the mcp-armor server?
mcp-armor is listed in the public MCP registry as io.studiomeyer/armor. Security sidecar for MCP servers: 11 read-only control-plane tools for prompt-injection checks. This page covers its container image (ghcr.io/studiomeyer-io/mcp-armor:0.8.0).
Is the mcp-armor server safe to use?
mcp-armor scores 46 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the mcp-armor server expose?
mcp-armor exposes 11 tools: armor_scan_payload, armor_verify_manifest, armor_list_blocked, armor_get_policy, armor_check_cve, and 6 more. Their descriptions and schemas cost roughly 683 tokens of context every time the server is loaded.
Is the mcp-armor server still maintained?
mcp-armor is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the mcp-armor server under?
mcp-armor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.