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/daedalus/mcp-registryWrote 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/daedalus/mcp-registry/mcp-registry)<a href="https://agentmods.dev/mcp/daedalus/mcp-registry/mcp-registry"><img src="https://agentmods.dev/badge/mcp/daedalus/mcp-registry/mcp-registry.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-registry 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 8d 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
{
"mcp-registry": {
"command": "uvx",
"args": [
"mcp-registry"
],
"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.
- 8d ago First seen · 9 lines scan A 93b7a3489766
mcp-registry is an MCP server published in the GitHub repository daedalus/mcp-registry (0 stars, last pushed 4mo 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
argus
Retrieval platform for AI agents — 14 search providers, 12-step content extraction, dead URL recovery, site capture, and local corpus storage. One API. Runs locally from the argus-search Python package. Needs 8 environment variables to run.
leaseclear-mcp
Standalone MCP server exposing LeaseClear Q&A as an MCP tool. Runs locally from the leaseclear-mcp Python package. Needs 2 environment variables to run.
presence-mcp
Launcher that exposes the presence Claude Code plugin's MCP server to any MCP-aware client. Runs locally from the presence-mcp Python package.
registry
The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server. Remote server at mcpqueen.com.
mcpexplorer
Search, vet & assemble MCP servers from your agent: verified tools, risk labels, and trust scores. Remote server at mcpexplorer.com.
preflight
Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm. Remote server at skillfoundry.synaplex.ai.