MoltPe
AI-native payment infrastructure that gives AI agents isolated wallets with programmable spending policies for autonomous USDC stablecoin transactions.
What it can do
- Check Balance: Returns the agent wallet's current USDC balance, daily spending limit, amount spent today, and remaining daily allowance.
- List Transactions: Returns recent transaction history for the agent wallet. Filter by status and control how many records are returned.
- Agent Info: Returns metadata about the agent: name, ID, wallet address, status, USDC balance, and spending limits.
What data it sees
Do you need an account
No: the server works without sign-in
AI-native payment infrastructure that gives AI agents isolated wallets with programmable spending policies for autonomous USDC stablecoin transactions.
11 MCP tools for Claude Desktop, Cursor, and Windsurf:
- check_balance, send_payment, list_transactions, agent_info
- create_invoice, pay_invoice, check_invoice_status, list_invoices
- call_x402_endpoint, call_mpp_endpoint, plus more
Tri-rail support: x402 (HTTP-native micropayments), MPP (session-based streaming), and traditional fiat. Multi-chain USDC on Polygon PoS, Base, and Tempo with sub-second settlement.
Non-custodial wallets with Shamir key splitting — your keys, never ours.
Programmable spending policies (daily caps, per-transaction caps, recipient allowlists, cooldowns) enforced at the infrastructure level. Your agent literally cannot overspend regardless of prompt injection or buggy retry loops.
Free tier — no credit card, no KYC, no geographic gating.
- Site: https://moltpe.com
- Open source reference: https://github.com/umangbuilds/moltpe-agent-payments (Apache 2.0)
- India guide: https://moltpe.com/india
- Developer quickstart: https://moltpe.com/blog/integrate-moltpe-in-5-minutes-developer-quickstart
How to connect
How to connect MoltPe to Claude
The server address to paste into Claude settings:
https://moltpe--umg-gpt.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect MoltPe to ChatGPT
The server address to paste into ChatGPT settings:
https://moltpe--umg-gpt.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect MoltPe to Cursor
The server address to paste into Cursor settings:
https://moltpe--umg-gpt.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (11)
Raw names from tools/list. Only developers need these.
| check_balance | Returns the agent wallet's current USDC balance, daily spending limit, amount spent today, and remaining daily allowance. |
| list_transactions | Returns recent transaction history for the agent wallet. Filter by status and control how many records are returned. |
| agent_info | Returns metadata about the agent: name, ID, wallet address, status, USDC balance, and spending limits. |
| send_payment | Sends a USDC payment from the agent wallet to a recipient address. Enforces per-transaction and daily spending limits. |
| call_x402_endpoint | Calls an x402-protected API endpoint. Automatically handles the HTTP 402 payment flow: probes the endpoint, pays if required, and returns the response data. If a matching Grantex spend grant exists, its JWT is auto-attached so servers can verify scope and budget. |
| list_active_grants | Returns the agent's active spend grants — endpoint, remaining budget, and expiry. An agent uses this to discover what it is pre-authorized to pay for. |
| create_invoice | Creates a USDC invoice for the agent. Returns a payment URL that can be shared with the payer. The payment is detected automatically when USDC arrives at the agent's wallet. |
| check_invoice_status | Checks the current status of an invoice. Returns amount, payment status, and payment URL. |
| list_invoices | Lists invoices created by this agent. Optionally filter by status (pending, partial, paid, expired, cancelled). |
| pay_invoice | Pay an invoice by invoice ID. The agent's wallet will be charged the invoice amount and the invoice will be marked as paid. |
| call_mpp_endpoint | Calls an MPP-paywalled HTTP endpoint. The agent pays using stablecoins on Tempo via the Machine Payments Protocol (MPP). Supports 100+ MPP-compatible services. The agent must be on a Tempo chain. |