RequestTap MCP Server

MCP server for the RequestTap API — the Agentic API Marketplace on Base.

Gives AI agents the ability to discover, call, and manage paid APIs on the RequestTap marketplace using the Model Context Protocol.

Tools

| Tool | Description | |------|-------------| | requesttap_discover | List all available paid APIs on the marketplace | | requesttap_discover_schema | Get MCP/A2A-compatible tool schema for all APIs | | requesttap_discover_tool | Get details for a single API tool | | requesttap_call | Call a paid API endpoint with x402 USDC payment | | requesttap_create_mandate | Create an AP2 spending mandate | | requesttap_list_mandates | List your spending mandates | | requesttap_get_mandate | Get mandate details | | requesttap_revoke_mandate | Revoke a spending mandate | | requesttap_receipts | Query transaction receipts | | requesttap_get_receipt | Get a single receipt | | requesttap_receipt_link | Get a receipt's hash-chain link |

Setup

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | REQUESTTAP_API_KEY | Yes (for gateway/mandate/receipt calls) | Your RequestTap agent API key (rta_...) | | REQUESTTAP_MANDATE_ID | No | Default AP2 mandate ID to include with requests | | REQUESTTAP_BASE_URL | No | API base URL (defaults to https://api.requesttap.ai) |

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "requesttap": {
      "command": "npx",
      "args": ["-y", "requesttap-mcp"],
      "env": {
        "REQUESTTAP_API_KEY": "rta_your_api_key_here",
        "REQUESTTAP_MANDATE_ID": "mnd_your_mandate_id"
      }
    }
  }
}

Cursor

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "requesttap": {
      "command": "npx",
      "args": ["-y", "requesttap-mcp"],
      "env": {
        "REQUESTTAP_API_KEY": "rta_your_api_key_here"
      }
    }
  }
}

Build from source

git clone https://github.com/RequestTap/RequestTap-MCP.git
cd RequestTap-MCP
npm install
npm run build

Authentication

• Discovery endpoints are public and require no authentication.
• Gateway calls require an API key (X-Api-Key) and x402 USDC payment token (X-402-Payment).
• Mandate and receipt endpoints require an API key or JWT.

Every successful gateway call returns a verifiable receipt in the x-receipt response header. Receipts are Keccak256 hash-chained for tamper-proof auditing.

License

MIT