Gatefare — paid-API marketplace

Name: Gatefare — paid-API marketplace
Author: gatefareio

@gatefareio

Gatefare — paid-API marketplace について

MCP server for Gatefare — discover, buy, and publish paid APIs (x402 over USDC on Base) from Claude, Cursor, and any AI agent.

#payments #crypto #web3 #agents #x402 #usdc #base #marketplace #discovery #mcp-server #non-custodial #api-marketplace #stablecoin-payments #micropayments #ai-agents #claude #cursor #coinbase

基本情報

カテゴリ

開発者ツール

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

gatefareio

投稿者

Gatefare

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "gatefare": {
      "command": "npx",
      "args": [
        "-y",
        "@gatefare/mcp"
      ],
      "env": {
        "GATEFARE_PAT": "<YOUR_GATEFARE_PAT>",
        "WALLET_PRIVATE_KEY": "<YOUR_WALLET_PRIVATE_KEY>",
        "WALLET_BUDGET_USD": "5.00",
        "WALLET_NETWORK": "eip155:8453"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Gatefare — paid-API marketplace?

Gatefare — paid-API marketplace is a Model Context Protocol (MCP) server that connects Claude Desktop, Cursor, or any MCP-compatible agent to the Gatefare catalog of paid HTTP APIs. Payments settle as USDC on Base via the open x402 standard, with no SaaS keys, subscriptions, or escrow. It is non-custodial: signing happens locally and the private key never leaves the machine.

How to use Gatefare — paid-API marketplace?

Configure the server in your client’s MCP config (Claude Desktop, Cursor, etc.) using the npx command npx -y @gatefare/mcp. Add optional environment variables like WALLET_PRIVATE_KEY for buying APIs or GATEFARE_PAT for publishing APIs. Tools auto-register based on which environment variables are set.

Key features of Gatefare — paid-API marketplace

Non-custodial: private key never leaves your machine
USDC settlement on Base via open x402 standard
13 tools across discovery, buyer, publisher, and safety domains
Tools auto-register based on environment configuration
Runtime budget safety cap (WALLET_BUDGET_USD)
Structured error codes for agent retry logic

Use cases of Gatefare — paid-API marketplace

Search the catalog and call a paid weather API in one conversation
Publish your own HTTP APIs for per‑call USDC pricing
Programmatically query and purchase APIs from an MCP‑compatible agent
Browse the catalog and estimate costs before buying

FAQ from Gatefare — paid-API marketplace

What networks does Gatefare support?

The default network is eip155:8453 (Base mainnet). For testing, set WALLET_NETWORK to eip155:84532 (Sepolia testnet).

What happens if I don't set a wallet key?

Without WALLET_PRIVATE_KEY, only discovery and safety tools are available. Buyer tools (call_api, get_wallet_balance, estimate_cost) are hidden.

How are payments secured?

The server signs an EIP‑3009 transferWithAuthorization that is single‑use and time‑bounded. The private key is never logged, and the server rejects network confusion attacks by verifying the configured chain.

Can I use this without an AI agent?

Yes. For paying x402 APIs from a backend, use Coinbase's official x402 SDKs. To browse the catalog programmatically, use the REST API at gatefare.io/api/catalog (OpenAPI 3.1 spec available).

What runtime does Gatefare depend on?

The server runs on Node.js via npx and is installed from npm as @gatefare/mcp. No additional runtime dependencies are required beyond a standard Node.js environment.