up2itnow0822/clawpay-mcp

Overview

An open-source, non-custodial payment layer that implements the x402 standard for AI agents using the Model Context Protocol (MCP). It enables pay-per-use interactions without central custody of funds, serving as an alternative to Vercel's x402-mcp implementation. Built in TypeScript, it integrates payments directly into agent workflows.

Best for

Best for
Developers building AI agents that need a self-hosted, non-custodial payment layer for pay-per-use interactions.

Use cases

• Monetizing AI agent interactions with per-request microtransactions
• Enabling payments in MCP-compatible agent toolchains or APIs
• Adding a non-custodial payment gate to autonomous agent services

How to use

Install

npx -y agentpay-mcp --version

Tools exposed

• AGENT_PRIVATE_KEY
• AGENT_WALLET_ADDRESS
• CHAIN_ID
• RPC_URL
• FACTORY_ADDRESS
• NFT_CONTRACT_ADDRESS
• SESSION_TTL_SECONDS

Tested with

Claude Desktop, Claude Code, Cursor, Windsurf

Example client config

{\n  "mcpServers": {\n    "agentpay": {\n      "command": "npx",\n      "args": ["agentpay-mcp"],\n      "env": {\n        "AGENT_PRIVATE_KEY": "0x...",\n        "AGENT_WALLET_ADDRESS": "0x..."\n      }\n    }\n  }\n}

Notes

An open-source, non-custodial payment layer that implements the x402 standard for AI agents using the Model Context Protocol (MCP). It enables pay-per-use interactions without central custody of funds, serving as an alternative to Vercel’s x402-mcp implementation. Built in TypeScript, it integrates payments directly into agent workflows.

4 stars on GitHub. Last updated 2026-05-19. Licensed MIT.

Use cases

• Monetizing AI agent interactions with per-request microtransactions
• Enabling payments in MCP-compatible agent toolchains or APIs
• Adding a non-custodial payment gate to autonomous agent services

Pros

• Non-custodial design keeps users in control of their funds
• Open-source alternative to a proprietary solution (Vercel x402-mcp)
• Written in TypeScript for broad compatibility in modern agent stacks

Cons

• Very low community traction (4 stars) indicates early-stage maturity
• Limited ecosystem support and likely sparse documentation
• Requires integration with both x402 and MCP infrastructure

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.