pick.tools

For vendors

pick.tools relays MCP calls from agents to the servers in its catalog. This page says how it reaches your server and how to change that.

How pick.tools calls your server

Every relayed request carries:

  • User-Agent: pick.tools/1 (+https://pick.tools/docs/for-vendors);
  • X-Forwarded-For: <the caller's IP>;
  • if your server needs a key, the caller's own key, placed where your server expects it (Headers);
  • any extra headers the caller sets as X-Pick-Header-<slug>-<name>, sent as <name>, except reserved names (connection and framing headers, the MCP transport's own, and pick.tools' own).

Requests go to the URL in the catalog and nowhere else; redirects to other hosts are not followed. pick.tools sends at most 8 relayed calls at a time to one server; probes are outside this cap.

Probes

Every catalogued server is probed hourly, with User-Agent: pick.tools-probe/1 (+https://pick.tools/docs/for-vendors). A probe sends initialize with no credential; when your URL has a {key} slot in its path or query, the probe fills it with the literal probe. For a keyless server it also runs tools/list. When pick.tools holds a probe key for your service, a second step sends a keyed initialize and tools/list. Probe results are public on your server's page and in the data API.

Egress IPs

pick.tools sends requests from 20.64.150.131.

Opt out

To stop relaying to your server, write from an address at your domain. Contact: not published yet. Within one business day your server is set to proxy: false: it stays listed with its own URL, so agents can still connect to it directly, and pick.tools no longer relays calls to it. If a standard opt-out signal appears, for example in a .well-known file, pick.tools will honour it too.

Get your tools listed

  • Keyless server: automatic. The hourly probe caches your tool names, titles, descriptions and input schemas.
  • Keyed server: the tools are cached when a caller with a key lists them, as the same metadata, never call arguments or results. To have them listed sooner, send us a key for an account of pick.tools' own with your service. It is used by the probe for tools/list, and never for other callers' calls.
  • Per-account tool lists: when your tools/list depends on the caller's account (as Zapier MCP's does), tell us. pick.tools then never caches or publishes a list a caller sees; each caller still gets its own list live.

What pick.tools never stores

Your users' keys, tool arguments and tool results. It stores one metadata row per call; Privacy lists the fields. URLs that hold a key are never logged.