About pick.tools
pick.tools is one MCP endpoint, https://pick.tools/mcp, where an agent searches, describes and calls tools on a curated catalog of remote MCP servers.
Every relayed call is counted, and the counts are published as rankings and as open data.
Who runs it
A single maintainer builds and runs pick.tools. There is no company, investor or sales team behind it.
What it does not do
- It does not store credentials. The key you send in an
X-Pick-Key-<slug>header goes to that vendor for that call and is not kept. - It does not store tool arguments or results.
- It does not relay OAuth servers in v1. For those, the agent gets the vendor's own URL.
How it is funded
It is not funded yet. No placement is sold: a vendor cannot pay to move up the rankings or to appear in search results. Rankings come from relayed calls, measured the same way for every server.
Other places to look
Other MCP directories, gateways and health monitors exist, and some publish usage or uptime numbers of their own. pick.tools is account-free and vendor-neutral: it has no gateway or vendor of its own to favour and sells no placement. It publishes its numbers as open data under CC BY 4.0, with the methodology behind them.
Read more
- Methodology: how every number is computed.
- For vendors: how pick.tools calls your server, and how to opt out.
- Privacy: what is stored per call, and what never is.
- Security: the pass-through model and its limits.
- Roadmap: what comes after v1.