PayAPI Market MCP server

Which servers in the official MCP registry are PayAPI Market's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to PayAPI Market

Whose server it is

Registry namemarket.payapi/marketplaceverified in the MCP registry

The registry name sits under payapi.market. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-12

Stateanswerschecked 2026-10-12
Tools3
Server calls itselfpayapi-market
Server version1.0.0
Protocol version2025-06-18

On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 101 ms.

Tools it offers3 tools · read 2026-10-12

search_apis
Free-text search across the live catalogue. Matches listing name, description, category and provider name. Returns settlement-verified listings only unless verified_only is false. Free and read-only; spends nothing.
list_apis
Browse the live catalogue, optionally filtered to one category. Omit category for everything. Returns settlement-verified listings only unless verified_only is false. Free and read-only; spends nothing.
get_api
Fetch a single live listing by its id or slug, including base_url, price range, network and verification state. payment_verified is true if at least one route was paid; verified_routes names each paid route with its on-chain receipt. Also…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "marketplace": {
      "type": "http",
      "url": "https://payapi.market/mcp"
    }
  }
}

OpenAPI spec

4 paths, read 2026-10-12. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.