A remote MCP registry server that lets an assistant search MCP servers by intent and retrieve their tools, connection details and readiness checks.
What you can do
Search servers and their tools with hybrid keyword and semantic search, filtered by connection class
Read one server's official server.json, connectability, current tools, trust breakdown and identity
List every current tool of a server with full input and output schemas, paginated by tool name
Get a minimal connection block for the preferred remote or package, with secret placeholders, formatted for a target client
Probe a remote MCP server URL once, credential-free, for quality checks and directory readiness
When to use it
Useful when you want an assistant to discover which MCP servers fit a task, compare their tools and connection options, or vet a remote server before adding it. It is a lookup and inspection service, not a proxy to the servers it lists.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. No authentication is declared, though check_server applies a quota of a few checks per hour anonymously, with more available otherwise.
Before you install
check_server sends a request to a server URL you supply, so only probe endpoints you are entitled to test. Connection blocks contain secret placeholders rather than values, and the server states that secrets are never accepted or returned. Quotas limit anonymous checks.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.protogrid%2Fregistry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Official server.json plus connectability (class, remotes with auth/health, packages), current tools, trust breakdown and identity for one server name.
Parametersnamerequiredschemas
list_tools
List a server's tools
Every current tool of a server with full input/output schemas, paginated by tool name.
Parametersnamerequiredlimitcursor
get_connection
Get a connection block
Minimal connection block for the preferred remote (or package) with ${SECRET} placeholders, formatted for a target client. Secrets are never accepted or returned.
Parametersnamerequiredtarget
check_server
Check an MCP server URL
Probe a remote MCP server URL once, credential-free and without calling its tools, and get its quality checks and its readiness for the Claude and OpenAI directories. Pass `url` to start a check (waits up to 25 s for the result), or `id` to read one. Quota: a few checks per hour anonymously, more with an API key.
Parametersidurlwait
Version history
1
v0.1.0LatestSep 23, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.