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-protocol-conformanceWrote 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-protocol-conformance/protocol-conformance)<a href="https://agentmods.dev/mcp/studiomeyer-io/mcp-protocol-conformance/protocol-conformance"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/mcp-protocol-conformance/protocol-conformance/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-protocol-conformance/protocol-conformance"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/mcp-protocol-conformance/protocol-conformance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
protocol-conformance 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 1mo 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
{
"protocol-conformance": {
"command": "npx",
"args": [
"-y",
"mcp-protocol-conformance"
],
"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.
- 1mo ago First seen · 10 lines scan A 59ad0ae10a24
protocol-conformance is an MCP server published in the GitHub repository studiomeyer-io/mcp-protocol-conformance (0 stars, last pushed yesterday), 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
hook-conformance
Audits MCP servers for Claude Code mcptool hook readiness: idempotency, latency, side-effects. Runs locally from the mcp-hook-conformance npm package.
cc-audit
MCP server "cc-audit" as configured in ryo-ebata/cc-audit. Launched with ./target/release/cc-audit serve.
wheel-hub
MCP server exposing wheelhub open-source evaluation to AI coding agents. Runs locally from the @wheel-hub/mcp npm package.
playwright
MCP server "playwright" as configured in evan043/claude-cli-advanced-starter-pack. Launched with cmd /c npx -y @anthropic/mcp-playwright.
slop-eval
Scores AI-generated UI for genericness ("slop") using an Anthropic LLM-judge rubric, with a --json mode for CI/agent quality gates and a documented programmatic API (scorecomposite, ScoreInput, LLMJudgeSource) for in-process use by agent frameworks. Runs locally from the slop-eval-cli Python package.
mcp-curate
Turn an OpenAPI spec into a high-quality, curated MCP server — with an eval harness that proves curation works. Runs locally from the mcp-curate Python package.