MCP.Market

Pay MCP server

by pay-skill·io.github.pay-skill/pay-mcp·v0.2.8
No reviews yet

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

B80/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Pay yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pay tools (15, 15 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • pay_discoverwrite action

    Search for paid API services that accept USDC payments.

  • pay_fundwrite action

    Generate a funding link to deposit USDC into your wallet.

  • pay_mintwrite action

    Mint testnet USDC (Base Sepolia only). Free test tokens with no real value.

  • pay_requestwrite action

    Make an HTTP request to a URL. If it returns 402 (Payment Required),

  • pay_sendwrite action

    Send a one-shot USDC payment to an address. Use this for single transfers,

  • pay_statuswrite action

    Check wallet balance and status. Shows USDC balance, open tab count,

  • pay_tab_chargewrite action

    Charge against an open tab. Only the provider can charge.

  • pay_tab_closewrite action

    Close a tab and settle funds. Either party can close unilaterally.

  • pay_tab_listwrite action

    List all tabs. Use to review tab health and optimize fund usage.

  • pay_tab_openwrite action

    Open a pre-funded metered tab with a provider. Use tabs for repeated API calls

  • pay_tab_topupwrite action

    Add more USDC to an open tab. Only the agent (tab opener) can top up.

  • pay_webhook_deletewrite action

    Delete a webhook registration by its ID.

  • pay_webhook_listwrite action

    List all registered webhooks for your wallet.

  • pay_webhook_registerwrite action

    Register a webhook to receive real-time payment event notifications.

  • pay_withdrawwrite action

    Generate a withdrawal link to pull USDC out of your wallet.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan33 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pay compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
100%
typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 15 change

Install Pay in Claude Code, Cursor or VS Code

Runs npx -y @pay-skill/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pay-mcp -- npx -y @pay-skill/mcp
Add to Cursor

What the publisher says

From the Pay repository's README, as published. We do not edit it. Read it on GitHub

@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 claudedesktopconfig.json:

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

VS Code / Cursor

Add to .vscode/mcp.json:

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

Claude Code

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

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, PAYSKILLSIGNERKEY is used as the decryption password.
  3. Raw hex key — If PAYSKILLSIGNERKEY 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:

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

Tabs (metered accounts)

Wallet

Discovery & Webhooks

Resources (5)

Prompts (3)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pay: common questions

Is Pay MCP server safe?
Mostly: it is graded B (80/100). Read the Pay safety report
How do I install Pay?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pay need an API key?
Yes. The registry entry asks for PAYSKILL_SIGNER_KEY.
Is Pay maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.2.8.
How does Pay compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.