mcpbeat Sign in

m2m.monster MCP Server

answering

m2m.monster is answering right now. Last checked 9 min ago. It exposes 10 tools.

Non-custodial x402 payments between AI agents on Solana. Returns unsigned transactions.

Uptime history 12 days of history · worst day 99%
12 days agonow
100.0%
Uptime 24h
182 of 182 checks
10
Tools
read from the server
257 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check m2m.monster every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add m2m-monster --transport http https://sandbox.m2m.monster/mcp
Settings → Connectors → Add custom connector, then paste this address
https://sandbox.m2m.monster/mcp
~/.codex/config.toml
[mcp_servers.m2m-monster]
url = "https://sandbox.m2m.monster/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "m2m-monster": {
      "url": "https://sandbox.m2m.monster/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "m2m-monster": {
      "type": "http",
      "url": "https://sandbox.m2m.monster/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

build
build_payment
Build the m2m-split transaction for a quote: the payer's transfer to the payee and the USDC fee transfer to the treasury, in one atomic transaction where the payer pays its own gas. Checks that the receiving token accounts exist and that the payer holds USDC for the fee, and simulates it. Unsigned. Sign it locally with your own Solana key; m2m.monster never sees or uses agents' private keys.
build_refund
Build a refund from the payee back to the payer, linked to the original receipt. The payee signs it and pays its gas; it has no m2m.monster fee and the original fee is not returned. Unsigned. Sign it locally with your own Solana key; m2m.monster never sees or uses agents' private keys.
verify
verify_payment
For the payee: check a payer-signed transaction against its quote (net amount, fee to the treasury, whitelisted mints, quote id and expiry) and simulate it before submitting.
verify_receipt
Verify a receipt: the m2m.monster signature and that the confirmed on-chain transaction matches it.
pricing
get_pricing
Agent-to-agent fee formula, referral program and the whitelisted token mints of this network.
quote
quote_payment
Price a payment to a payee: gross amount, net amount to the payee, fee_gross, discount, fee_net, treasury, mint and a 30-second expiry. Returns a signed quote.
referral
get_referral_status
Your referrer, referred agents, credits and their expiry dates. Credits are discounts on your own fees, never cash. Requires the api_key from register_agent.
register
register_agent
Optional registration; paying and getting paid work without it. It unlocks referral credits and receipt history. Call once without `signature` to get the message to sign with your Solana key, then again with the base58 signature to receive an api_key.
status
get_status
Service status and API version.
submit
submit_payment
Broadcast a transaction the payer already signed, wait for confirmation and return the signed receipt. Only broadcasts; never signs or pays payment transactions. A retry with the same idempotency_key never pays twice.

Endpoints

URLTransportStateLatencyChecked
https://sandbox.m2m.monster/mcp streamable-http answering 244 ms 9 min ago
https://api.m2m.monster/mcp streamable-http answering 212 ms 9 min ago

Alternatives to m2m.monster

same job, measured the same way
Xenarch MCP
by xenarch-ai

Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.

53 installs/wk local only
Agentpay
by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.

448 installs/wk local only
Clawpay
by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains.

local only
ClawPay MCP — Non-Custodial x402 Payments for AI Agents
by up2itnow0822

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

117 installs/wk local only
Clawswap
by wartech9

Cross-chain swaps between Solana and Base for AI agents paid for via via x402 micropayments.

29 installs/wk local only
A
agents.u.cash
by uxdevo

Non-custodial HTTP-402 crypto payments for AI agents. 79-tool MCP server.

local only
A
agents.u.cash
by uantum

Non-custodial HTTP-402 crypto payments for AI agents. 77-tool MCP server.

local only
x402 Merchant Check
by gradientdecisions

Pre-payment merchant trust checks for x402 agents on Base and Solana.

1 tools answering

m2m.monster — questions

Answers built from our own checks of this server.

What can m2m.monster do?
It exposes 10 tools, read directly from the server on our last check. Among them: build_payment, build_refund, get_pricing, get_referral_status, get_status, quote_payment and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is m2m.monster mostly used for?
Its tools cluster around build and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is m2m.monster working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 257 ms. The bar chart above shows every period we have measured.
How do I connect m2m.monster?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does m2m.monster need an API key?
No. m2m.monster completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is m2m.monster?
It answers our handshake in 257 ms on average, which is faster than 65% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.