PincerPay
@ds1
About PincerPay
On-chain USDC payment gateway for AI agents. x402 protocol.
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
26Returns supported blockchain networks and their USDC configurations. Includes Solana (primary), Base, and Polygon with mainnet/testnet variants. Shows chain shorthand, CAIP-2 ID, USDC contract address, and block time.
Estimate the gas/transaction fee for a USDC payment on a given chain. Returns the native gas token, estimated USD cost, and notes about Kora gasless transactions (Solana) or L2 gas optimization.
Check whether the PincerPay facilitator is reachable and healthy. Returns database status, worker health, uptime, and Kora (gasless) status. No API key required. Use this as the first troubleshooting step.
Fetch performance metrics from the PincerPay facilitator. Returns settlement counters, latency percentiles (p50/p95/p99), verification stats, and error rates. No API key required.
Query the PincerPay facilitator for the status of a payment transaction. Returns chain, amount, addresses, status (pending/mempool/optimistic/confirmed/failed), and timestamps. Requires a PincerPay API key.
Dry-run payment validation against the PincerPay facilitator without broadcasting. Checks signature validity, balance, and payment requirements. Requires a PincerPay API key. Useful for debugging payment failures.
List paywalled endpoints configured for your merchant account. Returns endpoint patterns, USDC amounts, chain overrides, and active status. Requires a PincerPay API key.
Create a new paywalled endpoint. Sets the USDC price and optional chain restrictions. The endpoint pattern must be unique per merchant. Requires a PincerPay API key.
Update an existing paywall's price, description, chains, or active status. Only provided fields are changed. Requires a PincerPay API key.
Permanently delete a paywalled endpoint. This cannot be undone. Use update-paywall with isActive=false to disable without deleting. Requires a PincerPay API key. Pass confirm=true to proceed.
List payment transactions for your merchant account with filtering and pagination. Returns chain, amount, status, gas costs, and timestamps. Requires a PincerPay API key.
List AI agents that have interacted with your merchant account. Shows Solana address, spending limits, Squads PDA, and status. Agents are auto-registered on first payment. Requires a PincerPay API key.
Update an agent's name, status, or spending limits. Set status to 'paused' or 'revoked' to block further payments. Spending limits are in USDC base units (6 decimals). Requires a PincerPay API key.
List webhook delivery attempts for your merchant account. Shows event type, HTTP status code, retry count, and delivery status. Useful for diagnosing missed webhook notifications. Requires a PincerPay API key.
Manually retry a failed or pending webhook delivery. Resets the delivery status and queues it for immediate retry. Cannot retry already-delivered webhooks. Requires a PincerPay API key.
Fetch your merchant profile including wallet address, supported chains, webhook URL, and on-chain registration status. Requires a PincerPay API key.
Validate a PincerPay merchant configuration object. Checks API key format, merchant address, route patterns, chain names, and USDC amounts. Returns validation results with specific error messages for each issue found.
Generate Next.js middleware code that adds x402 USDC payment walls to API routes. Produces a complete, copy-paste-ready code snippet with PincerPay SDK setup, route configuration, and environment variable usage. Uses a Hono adapter in a catch-all App Router route. Supports Solana (primary), Base, and Polygon chains. Pass `merchantAddresses` for multi-chain merchants, `merchantAddress` for single-chain.
Generate agent-side code that automatically handles x402 USDC payments. Produces a PincerPayAgent setup with wallet configuration and spending policies. The agent's fetch() is a drop-in replacement for standard fetch that handles 402 challenges automatically.
Generate a /.well-known/ucp JSON manifest for agent-readable commerce discovery. UCP (Universal Commerce Protocol) lets AI agents discover your API's payment requirements, supported chains, and endpoint pricing. Place the output at /.well-known/ucp on your domain.
Generates a non-custodial merchant wallet set: one BIP-39 mnemonic plus Solana + EVM addresses derived from it. Phantom and MetaMask compatible (Solana m/44'/501'/0'/0', EVM m/44'/60'/0'/0/0). Pure client-side crypto — PincerPay never sees the keys. Use this before bootstrap-merchant to provision wallets, or independently to generate any new keypair set.
End-to-end merchant onboarding: generates non-custodial wallets, creates a merchant record, and mints an API key in one call. Returns mnemonic + addresses + raw API key. Auth modes: (1) admin if DATABASE_URL is set on the MCP server, (2) public if ~/.pincerpay/credentials.json exists (run `npx @pincerpay/cli login` first). PincerPay never persists the mnemonic or private keys; the caller must display them once and discard.
Mints a new pp_live_* API key for the current merchant. The raw key is returned ONCE. Auth modes: (1) admin if DATABASE_URL is set, requires --merchant; (2) public if ~/.pincerpay/credentials.json exists, mints for the logged-in user's merchant.
Admin mode (DATABASE_URL): lists all merchants in the database. Public mode (CLI credentials): returns only the caller's own merchant.
Returns information about the currently authenticated user — auth mode (admin vs public), auth user id, session info, and current merchant. Useful diagnostic before mutating tools.
Returns instructions for authenticating the MCP server. Call this when an onboarding tool returns an auth error to guide the user through the right flow.
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.
Frequently asked questions
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.
Basic information
More Developer Tools MCP servers
CodeSentinel
icohangar-opsCodebase health as MCP tools: dead code, circular dependencies, coupling, architectural drift.
ZeroBeacon — 1000-Tool Collision-Proof Commerce Router
DavidFox998ZeroBeacon.ai — Collision-proof commerce router for AI agents. 1000 MCP tools: commerce, trust, billing, sovereign ID + everyday tools. LIVE.
Vibgrate MCP
VibgrateQuery your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

Routebase
RoutebaseRoutebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

CircleCI MCP Server
CircleCIManage CI/CD pipelines, debug failed builds, and optimize test suites directly from your AI agents - no terminal required. The CircleCI MCP Server is a remote server hosted by CircleCI that connects AI tools and agents
Comments