From the maker

API.market connects AI agents to an API marketplace through a proprietary hosted MCP gateway. Five tools let agents search APIs, inspect operation schemas, execute calls, check usage and manage subscriptions: search_apis, get_api_tools, call_api, check_usage and manage_subscription. Connect over Streamable HTTP at https://api.market/api/mcp/gateway using OAuth or an API key. An API.market account is required. Free tiers, quotas and paid plans vary by API; calls and subscription changes may incur charges. Setup documentation: https://api.market/mcp. The hosted server implementation is not open source. Anonymous requests correctly receive an authentication challenge; no credential is included in this listing submission.

How to connect

Streamable HTTP endpoint:

https://api.market/api/mcp/gateway

What happened when we asked

We asked on 25 September 2026 and it challenged us for credentials. That is a working server guarding itself: it answered, and it wants an account we do not hold. A tool count and a response time come from a tools/list we were never served, so this listing carries neither.

How it asks you to sign in

Its refusal named a public document describing how to authenticate, which is what the MCP authorization spec asks a guarded server to publish. We read that document on 25 September 2026. Everything below is what it says; we have still not been inside this server.

Sign in through

api.market

Token accepted in

header

Read

2026-09-25 09:34 UTC

The 1 permission it declares

These are the scopes the document lists, verbatim. They describe what an account can grant this server, not what it will do with the grant, and we have not audited either.

• mcp:use

Anything above describes one moment on the date shown. We do not re-test on a schedule, so nothing here says what this server is doing now. We have not audited its code, its data handling or its permissions, and this is not a safety rating.