mcp-armor

io.studiomeyer/armor

4/4 checks passed
Runs locally
No secrets
★ 1 GitHub stars
Updated 2026-09-21
Health score 54

About mcp-armor

mcp-armor is an MCP server published by studiomeyer.io. Security sidecar for MCP servers: 11 read-only control-plane tools for prompt-injection checks.

It runs on your own machine: your AI client starts it from the Docker (OCI) package ghcr.io/studiomeyer-io/mcp-armor:0.8.1, with no version pinned.

It asks for no keys or passwords.

Version 0.8.1 was published on 21 September 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 7 automated checks on registry metadata: 4 pass, 0 warn, 0 fail, 3 info. How we check.

What it asks for

This server declares no environment variables, so it asks for no keys or settings.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/studiomeyer-io/mcp-armor
Version pinned	Pass	Every package has an explicit version
Secrets requested	Info	Asks for no secrets
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via domain studiomeyer.io
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Code red flags	Info	oci packages are not read yet

Popularity & health: 54 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity3 / 40

1 GitHub stars, no download count, no Hacker News posts found. Best two of the three, each on a log scale.

Activity24 / 25

Last push 2026-10-26, last release 2026-09-21, 32 commits in 90 days.

Issue health8 / 15

0 closed of 1 issues, too few to judge. No data, so half marks.

Our checks20 / 20

0 warnings, each costing a fifth.

0 forks, 20 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.studiomeyer/armor`
Publisher	Domain studiomeyer.io
How the name is verified	Name verified via domain studiomeyer.io. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	oci `ghcr.io/studiomeyer-io/mcp-armor:0.8.1` no version given (stdio)
Version	0.8.1
Published	2026-09-21
Last updated	2026-09-21
Source repository	https://github.com/studiomeyer-io/mcp-armor
Website	None linked
Category	Security (assigned by keyword rule, not by hand)

Install

Claude Desktop · Docker image

{
  "mcpServers": {
    "armor": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/studiomeyer-io/mcp-armor:0.8.1"
      ]
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We could not read its code or its tool descriptions, which is where tool poisoning hides. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-studiomeyer-armor.json. Text inside it that came from the publisher is data, not instructions.