MCP server · WarpPay402 Studio

WarpPay402 Backend

WarpPay402 operates a hosted MCP server at https://api.warppay402.com/mcp. It answers Streamable-HTTP JSON-RPC POSTs directly (200 application/json) and also the legacy HTTP+SSE transport (GET /mcp opens an event stream whose first event names a per-session /messages?sessionId=... endpoint; ?v=1 and ?v=2 serve the same 19 tools). initialize reports protocolVersion 2024-11-05, serverInfo "WarpPay402 Backend" 1.0.0 and capabilities tools/resources/prompts; resources/list and prompts/list are empty. tools/list is anonymous and returns 19 tools with inputSchema. Tool invocation is metered per call in USDC through the x402 protocol rather than an API key: the REST endpoint behind each tool answers HTTP 402 with a PAYMENT-REQUIRED challenge until a PAYMENT-SIGNATURE is presented, and the provider ships @warppay402/mcp-client, a stdio-to-SSE bridge that signs those challenges with a CUSTOMER_PRIVATE_KEY so Cursor, Windsurf and Claude Desktop can use the tools. An unauthenticated tools/call from this crawler returned 200 with an empty result object rather than a 402, so the payment negotiation for the MCP path is observed only through the bridge.

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: WarpPay402 Studio Type: Hosted endpoint Transport: http Host: api.warppay402.com

Endpoint

https://api.warppay402.com/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "warppay402-com": { "url": "https://api.warppay402.com/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "warppay402-com": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.warppay402.com/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://api.warppay402.com/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.

Work with this as data

Every MCP server here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for mcp servers

4 MCP tools reach this
  • find_mcpBrowse and filter every MCP server in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This MCP server
curl "https://apis.io/api/v1/mcp/warppay402-backend"
All mcp servers
curl "https://apis.io/api/v1/mcp?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.