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/The-Code-Registry/mcp-serverWrote 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/the-code-registry/mcp-server/coderegistry)<a href="https://agentmods.dev/mcp/the-code-registry/mcp-server/coderegistry"><img src="https://agentmods.dev/badge/mcp/the-code-registry/mcp-server/coderegistry/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/the-code-registry/mcp-server/coderegistry"><img src="https://agentmods.dev/badge/mcp/the-code-registry/mcp-server/coderegistry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
coderegistry 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
{
"coderegistry": {
"url": "https://integrator.app.thecoderegistry.com/api/ai/router",
"type": "streamable-http"
}
}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 · 6 lines scan A 435493dded27
coderegistry is an MCP server published in the GitHub repository The-Code-Registry/mcp-server (1 stars, last pushed 3mo ago), 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
roam-code
MCP server "roam-code" as configured in Cranot/roam-code. Launched with roam mcp. Needs 1 environment variable to run.
euthynos
Euthynos — deterministic repository intelligence for AI coding agents (MCP server): exact source spans, call graphs, clone detection, honest evidence boundaries. Runs locally from the euthynos npm package.
ovecc
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate. Runs locally from the ovecc npm package.
sem
Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents. Runs locally from the @ataraxy-labs/sem npm package.
juror
MCP server "juror", hosted remotely at app.juror.dev, as configured in Juror-AI/juror.
codehelper
MCP server "codehelper" as configured in VeyrForge/codehelper. Launched with https://github.com/VeyrForge/codehelper/releases/download/v3.0.3/codehelper_3.0..