One MCP endpoint for many services
pick.tools is an MCP endpoint, https://pick.tools/mcp, where an agent searches, describes and calls tools on a curated catalog of remote MCP servers.
Calls to keyless servers are relayed as they are; calls to API-key servers carry the key you send in a request header, which pick.tools never stores; for an OAuth server the agent gets the vendor's own URL.
Every relayed call is counted, and the counts, success rates, latency and hourly health probes are published as open data under CC BY 4.0.
Connect
Claude Code
claude mcp add --transport http pick https://pick.tools/mcp
JSON config (mcpServers)
{
"mcpServers": {
"pick": {
"type": "http",
"url": "https://pick.tools/mcp"
}
}
}
A service that needs a key gets one header, X-Pick-Key-<slug>: <your key>; each server page names its exact header.
Hosted connectors that cannot set headers reach the keyless servers.
More in Getting started.
Top servers, last 7 days
No relayed calls yet. Rankings appear as traffic arrives.
| Server | Auth | Health |
|---|---|---|
| Blockscout | keyless | up |
| Cloudflare Docs | keyless | up |
| Context7 | keyless | up |
| DeepWiki | keyless | up |
| Exa | keyless | up |
| Firecrawl | API key | up |
| Hugging Face | keyless | up |
| Jina AI | keyless | up |
| Kagi | API key | up |
| Microsoft Learn | keyless | up |
Last 7 days: 0 calls relayed · 0 answered · 0 servers with traffic