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.
npx agentmods add mcp/studiomeyer-io/mcp-hook-conformance/hook-conformancegit clone --depth 1 https://github.com/studiomeyer-io/mcp-hook-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-hook-conformance/hook-conformance)<a href="https://agentmods.dev/mcp/studiomeyer-io/mcp-hook-conformance/hook-conformance"><img src="https://agentmods.dev/badge/mcp/studiomeyer-io/mcp-hook-conformance/hook-conformance.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hook-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 5d 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
{
"hook-conformance": {
"command": "npx",
"args": [
"-y",
"mcp-hook-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.
- 5d ago First seen · 10 lines scan A 6e03faaadd16
hook-conformance is an MCP server published in the GitHub repository studiomeyer-io/mcp-hook-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
protocol-conformance
MCP conformance test harness. JSON-RPC, OAuth 2.1 PKCE, schemas, smoke, annotations. CLI + lib. Runs locally from the mcp-protocol-conformance 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.
runecho
MCP server "runecho" as configured in inth3shadows/runecho. Launched with ${RUNECHO_MCP_COMMAND:-runecho-mcp}.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.