Categories › AI & Agents › Multi-agent, orchestration & workflows
Find MCP servers by intent and get exactly how to connect to them right now. No proxying.
Remote server: your requests and data go to api.protogrid.dev. Claude Code: claude mcp add --transport http protogrid https://api.protogrid.dev/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search — Hybrid (keyword + semantic) search over servers and their tools. Filter by connection class to keep only what you can reach autonomously (R0get_server — Official server.json plus connectability (class, remotes with auth/health, packages), current tools, trust breakdown and identity for one selist_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 nevergate — Pass or fail for one server against the rules you name (at least one), with every rule it broke: minimum quality or trust, checks that must 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 ClauNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.