A query-parameter credential is the easiest possible setup — paste one string and you are connected — and it is also the credential most likely to end up in a log, a browser history or a screenshot of a config file. The platform's own documentation offers general API-key hygiene and nothing MCP-specific, so the handling is on you. Treat the whole URL as the secret and rotate it like one.
A marketplace where each published API gets its own MCP address. There is no single endpoint — you build the URL from the API's slug and your key.
Whatever the API you connected exposes. The catalogue is the product, so the tool surface is defined by the individual API rather than by the platform.
An API key, passed in the URL's query string. Personal is free with 500 requests a day, Team is $7 per user per month with 2,000; individual APIs price separately, from free to consumption-based, with prepaid credits that auto top-up below $5.
Paste a URL with a key — add the endpoint to your client