Pay Mcp

io.github.pay-skillPublished by GitHub account pay-skillv0.2.8Updated Oct 24, 2026

USDC payments for AI agents on Base — direct, tabs, x402 paywalls, discovery

VerifiedSTDIODesktop onlyFinanceDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant send and receive USDC payments on Base, manage metered tabs, and pay x402-gated APIs.

What you can do
Provides 15 tools for USDC payments on Base: direct sends, HTTP requests with automatic x402 payment handling, and metered tabs that providers charge per call. Wallet tools cover balance and status, funding and withdrawal links, and testnet USDC minting. It also offers service discovery for paid APIs and webhook registration for payment events, plus wallet and tab resources and guided prompts.
When to use it
Use it when an assistant needs to pay for APIs or services with USDC on Base, settle x402 paywalls, or run prepaid metered accounts with providers. It suits agent workflows that spend real funds and need balance, tab, and webhook visibility.
Requirements
Runs locally over stdio, typically via npx @pay-skill/mcp, on desktop clients such as Claude Desktop, Cursor, VS Code, or Claude Code. Node.js and network access to the Pay API are needed. On first run it generates a wallet and stores it in the OS keychain; PAYSKILL_SIGNER_KEY is an optional override and PAY_NETWORK selects mainnet or testnet.
Before you install
This server moves real money: it sends USDC, opens pre-funded tabs, and can auto-pay x402 requests, with confirmation thresholds of under $10 automatic, $10-100 planned, and over $100 explicit. PAYSKILL_SIGNER_KEY is a private key or keystore password that grants wallet control; keep it out of shared configs. Funding and withdrawal links are time-limited, and webhooks are registered with third parties.

Installation

In SourceWeft

  1. Open Pay Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@pay-skill/mcp

MCP server for Pay -- the complete x402 payment stack for AI agents. USDC on Base.

Gives any MCP-compatible client (Claude Desktop, Cursor, VS Code, custom frameworks) the full power of Pay: direct payments, tabs, x402 paywalls, service discovery, and wallet management. No CLI binary needed.

Setup

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "pay": {      "command": "npx",      "args": ["-y", "@pay-skill/mcp"]    }  }}

VS Code / Cursor

Add to .vscode/mcp.json:

json
{  "servers": {    "pay": {      "command": "npx",      "args": ["-y", "@pay-skill/mcp"]    }  }}

Claude Code

bash
claude mcp add pay -- npx -y @pay-skill/mcp

That's it. On first run, the server generates a wallet and stores it in the OS keychain (Windows Hello, macOS Keychain, Linux Secret Service). Subsequent runs load it automatically.

Configuration

Env VarRequiredDefaultDescription
PAYSKILL_SIGNER_KEYNo—Optional override. Raw hex key or .enc keystore password. Not needed for normal use.
PAY_NETWORKNomainnetmainnet (Base) or testnet (Base Sepolia)

Key Resolution (checked in order)

  1. OS keychain (default) — Loads from the OS credential store via keytar. On first run, a new keypair is generated and stored automatically.
  2. Encrypted keystore — If ~/.pay/keys/default.enc exists, PAYSKILL_SIGNER_KEY is used as the decryption password.
  3. Raw hex key — If PAYSKILL_SIGNER_KEY is a 64-char hex string, it's used directly. For dev/testing or importing an existing wallet.
  4. Auto-generate — If none of the above, generates a new keypair and stores it in the OS keychain.

Diagnostic Check

Verify everything is configured correctly:

bash
npx @pay-skill/mcp --check

Output:

pay-mcp diagnostic check  network: Base (chain 8453)  api:     https://pay-skill.com/api/v1  wallet:  0x1234...  key:     keychain  server:  OK (router: 0xABCD...)  auth:    OK (balance: $50.00)
All checks passed. MCP server is ready.

Tools (15)

Payments

ToolDescription
pay_sendDirect USDC payment ($1 min). Confirmation thresholds: <$10 auto, $10-100 plan, >$100 explicit.
pay_requestHTTP request with x402 auto-payment. Handles 402 detection, direct/tab settlement, price skepticism.

Tabs (metered accounts)

ToolDescription
pay_tab_openOpen pre-funded tab ($5 min, $50 recommended). Provider charges per-call.
pay_tab_closeClose tab. Returns distribution breakdown (provider 99%, fee 1%, agent remainder).
pay_tab_chargeCharge against open tab (provider only).
pay_tab_topupAdd funds to open tab (agent only).
pay_tab_listList tabs with idle/low-balance flags.

Wallet

ToolDescription
pay_statusBalance, locked/available funds, actionable suggestions.
pay_fundGenerate 1-hour funding link (Coinbase Onramp or direct USDC).
pay_withdrawGenerate 1-hour withdrawal link.
pay_mintMint testnet USDC (Base Sepolia only).

Discovery & Webhooks

ToolDescription
pay_discoverSearch paid API services by keyword/category.
pay_webhook_registerRegister webhook for payment events (HMAC-signed).
pay_webhook_listList registered webhooks.
pay_webhook_deleteDelete a webhook.

Resources (5)

URIDescription
pay://wallet/statusBalance, tabs, locked/available
pay://wallet/tabsAll open tabs
pay://tab/{tab_id}Single tab detail
pay://wallet/addressWallet address
pay://networkNetwork config + contract addresses

Prompts (3)

PromptDescription
pay-for-serviceGuided: discover service, evaluate pricing, make request
review-tabsReview tabs, flag idle, suggest close/topup
fund-walletGenerate fund link, explain deposit process

Development

bash
git clone https://github.com/pay-skill/pay-mcp.gitcd pay-mcpnpm installnpm run buildnpm test                    # unit tests (mocked)npm run test:acceptance     # testnet (requires PAYSKILL_TESTNET_KEY)

License

MIT

Part of Pay

Pay is the complete x402 payment stack -- gateway, facilitator, SDKs, CLI, and MCP server -- that lets AI agents pay for APIs with USDC on Base.

Source: README.md at commit 9dd2d20

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.8LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.