mcp-registry-search
Enables AI agents to dynamically discover, search, and inspect every MCP server in the official Model Context Protocol registry at runtime.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
Spacemandomains
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
search_mcp_registryFind servers by keyword or name (e.g. 'weather', 'github', 'database'). Returns matching servers with their endpoint URL, transport type, and description.
get_mcp_server_detailsGet full metadata for a specific MCP server by its reverse-DNS registry name (e.g. io.github.username/server-name). Returns all versions, remotes, packages, and tools.
list_mcp_serversBrowse all MCP servers in the registry with pagination. Use the next_cursor from the response to fetch subsequent pages.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Next.js: Server-Side Request Forgery in Server Actions on custom servers
Next.js: Denial of Service in App Router using Server Actions
Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
Next.js: Unbounded Server Action payload in Edge runtime
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
3/3 tools missing one or more hints — search_mcp_registry (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_mcp_server_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_mcp_servers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 3 high severity in production deps — next@15.5.18 (high), next@15.5.18 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/spacemandomains/mcp-registry-search)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check