MCP.so
Sign In

PincerPay

@ds1

About PincerPay

On-chain USDC payment gateway for AI agents. x402 protocol.

Basic information

Category

Developer Tools

License

MIT

Runtime

node

Transports

stdio

Publisher

ds1

Submitted by

DS1

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "pincerpay": {
      "command": "npx",
      "args": [
        "-y",
        "@pincerpay/mcp"
      ],
      "env": {
        "PINCERPAY_FACILITATOR_URL": "https://facilitator.pincerpay.com",
        "PINCERPAY_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is PincerPay?

PincerPay is a non-custodial x402 payment facilitator that lets merchants accept payments from AI agents. It settles instantly in USDC and integrates via HTTP 402 challenges. The PincerPay MCP server exposes 26 tools for AI assistants to manage onboarding, wallets, and merchant operations.

How to use PincerPay?

Install the MCP server package (@pincerpay/mcp) and use it with an AI assistant. Onboarding is done entirely via the terminal using npx @pincerpay/cli signup and npx @pincerpay/cli bootstrap-merchant. The same flows are available as MCP tools (bootstrap-wallets, bootstrap-merchant, create-api-key, list-merchants).

Key features of PincerPay

  • Non-custodial: private keys never leave the user’s machine
  • x402 facilitator: automated HTTP 402 payment challenge handling
  • Multi-chain support: Solana, Base, and Polygon
  • Instant settlement in USDC
  • Terminal-only merchant onboarding (no browser required)
  • Merchant SDK with Express and Hono middleware
  • Agent SDK with automatic 402 payment handling
  • MCP server with 26 tools for AI assistant integration

Use cases of PincerPay

  • AI agents paying for access to merchant APIs (e.g., weather data endpoints)
  • Merchants accepting payments from AI agents without manual intervention
  • Terminal-only provisioning of merchant wallets, API keys, and storefronts

FAQ from PincerPay

How does PincerPay handle payments?

When an AI agent hits a merchant API and receives HTTP 402, the agent signs a USDC transfer. PincerPay verifies the signature, broadcasts it to the blockchain, and confirms settlement.

What blockchains are supported?

Solana (mainnet, devnet), Base (mainnet, Sepolia), and Polygon (mainnet, Amoy). Solana is the primary chain; Base and Polygon are optional secondary chains.

Is PincerPay non-custodial?

Yes. Wallets are generated locally on the user’s machine. PincerPay never sees or stores private keys.

What are the prerequisites for running the server?

Node.js 22+, pnpm 10+, and a PostgreSQL database (Supabase recommended). The facilitator runs on Railway, the dashboard on Vercel.

How do I onboard as a merchant?

Use the terminal: npx @pincerpay/cli signup (email + password + 6-digit code), then npx @pincerpay/cli bootstrap-merchant to generate wallets, create the merchant, and mint an API key.

Comments

More Developer Tools MCP servers