io.github.Spacemandomains/mcp-registry-search

MCPcommunitylive
v1.0.9io.github.SpacemandomainsUnknownUpdated 4mo agoGitHub

Search and browse every MCP server in the Model Context Protocol registry.

One connection. Access to every MCP server in the official MCP registry. Transport: streamable-http Registry: io.github.Spacemandomains/mcp-registry-search Gives any AI agent or LLM the ability to dynamically discover, search, and inspect every server in the official Model Context Protocol registry — at runtime, with no hardcoded tool knowledge. 1. listmcpservers — paginate the full registry 2.…

Endpoint healthlive
checked 8 days ago · 879ms
80% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
4mo agoLast update
Package
Authorio.github.Spacemandomains
LicenseUnknown
Version1.0.9
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface3 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_mcp_registryNo description published

This tool published no description. Forge does not invent one.

get_mcp_server_detailsNo description published

This tool published no description. Forge does not invent one.

list_mcp_serversNo description published

This tool published no description. Forge does not invent one.

0 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

One connection. Access to every MCP server in the official MCP registry. Transport: streamable-http Registry: io.github.Spacemandomains/mcp-registry-search Gives any AI agent or LLM the ability to dynamically discover, search, and inspect every server in the official Model Context Protocol registry — at runtime, with no hardcoded tool knowledge. 1. listmcpservers — paginate the full registry 2. getmcpserverdetails — get full metadata for any server by reverse-DNS name 3. searchmcp_registry —…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in search & retrieval