
M2mcent
io.github.EvozimPublished by GitHub account Evozimv1.0.5Updated Oct 24, 2026
x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.
Overview
M2mcent is an x402 payment wrapper SDK that lets an assistant or MCP server charge USDC micropayments on Base L2 for protected API endpoints.
- What you can do
- Wrap Express API or MCP tool endpoints behind a USDC paywall with a single requirePayment call
- Return HTTP 402 payment metadata and accept signed EIP-712 / EIP-3009 authorizations from paying agents
- Settle payments atomically on-chain through the M2mcent escrow contract on Base Mainnet
- Hand back the premium response together with the settlement transaction receipt
- No individual tools are listed in the manifest; the package is a library used inside your own server code.
- When to use it
- Use it when you are building an API or MCP server and want to charge other agents per request in USDC on Base, or when you need a drop-in x402 paywall for existing endpoints.
- Requirements
- Runs locally as an npm package (m2mcent-sdk) over stdio. Needs a Base Mainnet RPC endpoint URL (BASE_RPC_URL), a relayer wallet private key (RELAYER_PRIVATE_KEY) and a treasury address (TREASURY_ADDRESS). Requires network access to Base and a funded relayer wallet for settlement.
Installation
In SourceWeft
- Open M2mcent in the dashboard and add it to a workspace.
- 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
🛰️ M2MCent SDK — x402 Payment Wrapper for AI Agents
[npm version] [License: MIT] [Base Mainnet]
Ultra-lightweight x402 payment interceptor for AI Agents and MCP Servers. Monetize any API in 3 lines of code.
🚀 Quick Start
📐 How It Works
M2MCent implements the x402 Payment Protocol — a machine-native payment standard inspired by HTTP 402:
- Agent requests a protected endpoint
- Server responds with
402 Payment Required+ payment metadata (Base64 encoded) - Agent signs an EIP-712 typed data authorization (gasless for the payer)
- Server settles atomically on-chain via the M2MCent Escrow contract
- Agent receives the premium response + transaction receipt
⚙️ Configuration
🔒 Security
- Non-custodial: Funds flow directly from payer → treasury via on-chain escrow
- Gasless for payers: Uses EIP-3009
transferWithAuthorization(USDC native) - Zero-Leak: No agent data is retained after settlement
- Atomic: Payment and service delivery happen in a single request cycle
🌐 Network Details
🧩 MCP Server Integration
Perfect for Model Context Protocol servers:
📊 Ecosystem
M2MCent powers 100+ production MCP servers on Base Mainnet, processing real USDC micro-payments for AI-to-AI commerce.
📄 License
MIT © M2MCent
Source: README.md at commit 88718c8
Tools
0Version history
1- v1.0.5LatestSep 16, 2026
Score
50% 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