MCP.Market

ClawPay MCP — Non-Custodial x402 Payments for AI Agents MCP server

by up2itnow0822·io.github.up2itnow0822/clawpay-mcp·v1.2.0·8 stars
No reviews yet

Non-custodial x402 payments for AI agents. Sign locally, spend limits, Base network.

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

full report

Adoption
Growing

8 stars48 downloads/wk

Reviews

Write one

Nobody has reviewed ClawPay MCP — Non-Custodial x402 Payments for AI Agents yet.

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

ClawPay MCP — Non-Custodial x402 Payments for AI Agents tools (11, 3 write)

write = sends, deletes, buys or posts

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

  • check_spend_limit

    Check whether a proposed payment amount is within the wallet's autonomous spend limits.

  • deploy_walletwrite action

    Deploy a new AgentAccountV2 wallet via the factory contract.

  • get_transaction_history

    Retrieve the wallet's recent on-chain transaction history from event logs.

  • get_wallet_info

    Get comprehensive wallet information including address, on-chain balance,

  • queue_approval

    Manage over-limit transactions queued for owner review.

  • send_paymentwrite action

    Send ETH or ERC20 tokens from the Agent Wallet.

  • x402_paywrite action

    Fetch a URL and automatically handle HTTP 402 Payment Required responses.

  • x402_session_end

    Explicitly close an x402 V2 session before it expires naturally.

  • x402_session_fetch

    Make an HTTP request within an established x402 V2 session — NO payment required.

  • x402_session_start

    Establish an x402 V2 payment session: make a SINGLE on-chain payment and receive

  • x402_session_status

    Check the status of x402 V2 payment sessions.

Public scan report

scanner v0.1.10 · 2026-11-12 · same rubric, same numbers if you re-run it

no findings
  • Code scan24 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 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ClawPay MCP — Non-Custodial x402 Payments for AI Agents compares

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

Safety score
83/100
higher than 65% of 48,114 servers
Tools
11
the typical server has 7
Tools that change things
27%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
8
more than 86% of 28,851 servers
Downloads a week
48
more than 25% of 15,093 servers with a package

What its tools let an agent do: 8 read · 1 change · 1 send or post · 1 run or deploy

Install ClawPay MCP — Non-Custodial x402 Payments for AI Agents in Claude Code, Cursor or VS Code

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

claude mcp add clawpay-mcp -- npx -y clawpay-mcp
Add to Cursor

What the publisher says

From the ClawPay MCP — Non-Custodial x402 Payments for AI Agents repository's README, as published. We do not edit it. Read it on GitHub

AgentPay MCP

AgentPay MCP is a stdio Model Context Protocol server for x402 payments and wallet operations. It exposes Agent Wallet SDK functions as MCP tools and loads a caller-controlled signing key from the local process environment.

The current npm package is agentpay-mcp v4.1.17.

Start without funds

Check the installed command without loading wallet credentials:

npx -y agentpay-mcp --version
npx -y agentpay-mcp --help

Use the AgentPay Wallet Starter for a no-funds verification of allowed, approval-required, and blocked policy outcomes.

MCP client configuration

Wallet tools read the following environment variables:

Example MCP configuration:

{
  "mcpServers": {
    "agentpay": {
      "command": "npx",
      "args": ["-y", "agentpay-mcp"],
      "env": {
        "AGENT_PRIVATE_KEY": "<secret-reference-or-local-key>",
        "AGENT_WALLET_ADDRESS": "0x<deployed-wallet-address>",
        "CHAIN_ID": "84532"
      }
    }
  }
}

Do not commit a real signing key. Use the client or operating system's secret mechanism where one exists. Start on Base Sepolia before using Base mainnet.

Tool groups

The tool registry in src/index.ts exposes these groups:

Tool schemas and handlers live under src/tools/.

Security boundaries

These boundaries matter more than the feature list:

viem for signing. Protect the process, environment, and MCP client config.

  • The server reads AGENTPRIVATEKEY into its local Node.js process and uses

call that tool again, and a process restart clears its rolling state.

  • setspendpolicy stores policy in the MCP server process. The same agent can

this is still application-level enforcement.

  • Every current value-moving handler calls the in-process policy check, but

AgentAccountV2. setspendpolicy does not write those contract limits.

  • On-chain limits exist only when the wallet owner configures them directly on

separate from the agent key.

  • An over-limit transaction is a human gate only when the owner key is kept

request log and does not record rejected pre-chain attempts or read-only calls.

  • gettransactionhistory reads on-chain wallet events. It is not an MCP

Sepolia. Unsupported chain IDs fail closed in src/utils/client.ts.

  • Runtime wallet configuration currently supports Base mainnet and Base

with bounded values and independent wallet limits.

  • Swap, bridge, escrow, and payment tools can move funds and consume gas. Test

Shortened. The full README is on GitHub.

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

ClawPay MCP — Non-Custodial x402 Payments for AI Agents: common questions

Is ClawPay MCP — Non-Custodial x402 Payments for AI Agents MCP server safe?
Mostly: it is graded B (83/100). Read the ClawPay MCP — Non-Custodial x402 Payments for AI Agents safety report
How do I install ClawPay MCP — Non-Custodial x402 Payments for AI Agents?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does ClawPay MCP — Non-Custodial x402 Payments for AI Agents need an API key?
Yes. The registry entry asks for AGENT_PRIVATE_KEY.
Is ClawPay MCP — Non-Custodial x402 Payments for AI Agents maintained?
The last commit was 6 days ago (2026-11-09). The latest release is v1.2.0.
How does ClawPay MCP — Non-Custodial x402 Payments for AI Agents compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,114 servers); tools 11 (the typical server has 7); tools that change things 27% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from up2itnow0822 →