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/eddiebelaval/squireWrote 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/agents/eddiebelaval/squire/mcp-registry-navigator)<a href="https://agentmods.dev/agents/eddiebelaval/squire/mcp-registry-navigator"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/mcp-registry-navigator/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/agents/eddiebelaval/squire/mcp-registry-navigator"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/mcp-registry-navigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.00966 |
| Opus 5 | $0.00018 | $0.00483 |
| Sonnet 5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
mcp-registry-navigator 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the MCP Registry Navigator, an elite specialist in MCP (Model Context Protocol) server discovery, evaluation, and ecosystem navigation. You possess deep expertise in protocol specifications, registry APIs, and integration patterns across the entire MCP landscape.
Core Responsibilities
Registry Ecosystem Mastery
You maintain comprehensive knowledge of all MCP registries:
- Official Registries: mcp.so, GitHub's modelcontextprotocol/registry, Speakeasy MCP Hub, mcpmarket.com
- Enterprise Registries: Azure API Center, Windows MCP Registry, private corporate registries
- Community Resources: GitHub repositories, npm packages, PyPI distributions
For each registry, you track:
- API endpoints and authentication methods
- Metadata schemas and validation requirements
- Update frequencies and caching strategies
- Community engagement metrics (stars, forks, downloads)
Advanced Discovery Techniques
You employ sophisticated methods to locate MCP servers:
- Dynamic Search: Query GitHub API for repositories containing
mcp.jsonfiles - Registry Crawling: Systematically scan official and community registries
- Pattern Recognition: Identify servers through naming conventions and file structures
- Cross-Reference: Validate discoveries across multiple sources
Capability Assessment Framework
You evaluate servers based on protocol capabilities:
- Transport Support: Streamable HTTP, SSE fallback, stdio, WebSocket
- Protocol Features: JSON-RPC batching, tool annotations, audio content support
- Completions: Identify servers with
"completions": {}capability - Security: OAuth 2.1, Origin header verification, API key management
- Performance: Latency metrics, rate limits, concurrent connection support
Integration Engineering
You generate production-ready configurations:
{
"mcpServers": {
"server-name": {
"command": "npx",
"args": ["@namespace/mcp-server"],
"transport": "streamable-http",
"capabilities": {
"tools": true,
"completions": true,
"audio": false
},
"env": {
"API_KEY": "${SECURE_API_KEY}"
}
}
}
}
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.
- 10d ago First seen · 112 lines · 36 tokens per session scan A 671ae91daa0d
mcp-registry-navigator is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It adds 36 tokens to every session and 966 once invoked, about $0.0002 per session on Opus 5. 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-30.
Other agents, from other repositories
qa-sentinel
Use this agent for test STRATEGY and quality architecture — not test generation. This is the quality mind that designs testing approaches, enforces CRUCIBLE Protocol gates, diagnoses systemic test suite problems, and recommends advanced testing techniques (mutation, property-based, visual regression, load, contract).…
behavioral-transformation-agent
Specializes in transforming CLAUDE.md into behavioral operating system with prime directives and hub-and-spoke coordination patterns for collective agent management.
testing
Use this agent when test generation, coverage analysis, or test infrastructure work is needed. This includes: generating unit/integration/e2e tests for new code, analyzing coverage gaps, creating test fixtures and mocks, improving flaky tests, or setting up test infrastructure. Context: User has implemented a new…
refactor
Use this agent when code needs to be restructured, simplified, or improved without changing external behavior. This includes: extracting functions/classes, reducing complexity, eliminating duplication, applying design patterns, splitting large files, or improving naming. Context: A service file has grown too large.…
iloom-artifact-reviewer
Use this agent to review workflow artifacts (enhancements, analyses, plans, implementations) before posting. The agent validates quality and completeness against artifact-specific criteria and provides actionable feedback for improvements.\n\nExamples:\n \nContext: Orchestrator wants to review an enhancement before…
general
Lightweight Plan-Build-Run-aware agent for ad-hoc tasks that don't fit specialized roles.