The appeal is obvious: enable a server in the dashboard and every client that already points here can use it, with no config edits and no restart. The trade is that nothing about the tool surface is stable enough to document — including for us, which is why the count here is Agent Store's and carries their date. The one-time-token path is worth noting if you run headless agents, since it avoids storing a long-lived key next to the code.
A multi-tenant gateway rather than a single server. Agent Store's own catalogue reported 43 MCP servers and 225 tools running behind this one address on 16 August 2026, and what you see depends on what your account has enabled.
Whatever the servers you have enabled expose — the tool surface is not fixed, which is the point of a gateway. The 225 figure is the vendor's own count across the catalogue, not a list we obtained from the endpoint.
An account, then one of three ways in: OAuth 2.1 with dynamic client registration, an X-API-Key header using an as_live_ key, or a one-time-token exchange for headless agents.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen