NestDaddy

protogrid

dev.protogrid/registry · v0.1.0

Find MCP servers by intent and get exactly how to connect to them right now. No proxying.

Connect Remote server

Terminal
claude mcp add --transport http registry https://api.protogrid.dev/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "registry": {
      "url": "https://api.protogrid.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "registry": {
      "type": "http",
      "url": "https://api.protogrid.dev/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://api.protogrid.dev/mcp

Tools 5 found in our last check

  • search

    Hybrid (keyword + semantic) search over servers and their tools. Filter by connection class to keep only what you can reach autonomously (R0, R1).

  • get_server

    Official server.json plus connectability (class, remotes with auth/health, packages), current tools, trust breakdown and identity for one server name.

  • list_tools

    Every current tool of a server with full input/output schemas, paginated by tool name.

  • get_connection

    Minimal connection block for the preferred remote (or package) with ${SECRET} placeholders, formatted for a target client. Secrets are never accepted or returned.

  • check_server

    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…

Details

Endpointhttps://api.protogrid.dev/mcp (Streamable HTTP)
First published23 Sep 2026
Last updated23 Sep 2026
Registry namedev.protogrid/registry

More search and web servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.