Clawpay runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 1 Nov 2026.
Non-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains.
What the code does
We read the source, 3 h ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Failure handler — create or update daily-review-failed issue
if: ${{ failure() && steps.preflight.outcome == 'success' }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check Clawpay every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to Clawpay
same job, measured the same wayNon-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.
Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.
Non-custodial HTTP-402 crypto payments for AI agents. 79-tool MCP server.
Non-custodial HTTP-402 crypto payments for AI agents. 77-tool MCP server.
Agent-commerce MCP server for x402/USDC payments and affiliate splits on Base.
x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.
Non-custodial x402 payments for AI agents. Sign locally, spend limits, Base network.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
Clawpay — questions
Answers built from our own checks of this server.