Remote MCP · Endpoint

m2m.monster MCP server

No. m2m.monster answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://api.m2m.monster/mcp

The last check completed an MCP handshake.

Registry name
monster.m2m/m2m-monster
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
281 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Non-custodial x402 payments between AI agents on Solana. Returns unsigned transactions.
Website
https://m2m.monster/
Listing
From the official MCP registry (active).
Recent checks of m2m.monster
CheckedResultHandshake
18 minutes agoHandshake completed281 ms
9 days agoHandshake completed273 ms
9 days agoHandshake completed279 ms
11 days agoHandshake completed284 ms
12 days agoHandshake completed282 ms
13 days agoHandshake completed347 ms
14 days agoHandshake completed569 ms
14 days agoHandshake completed274 ms
16 days agoHandshake completed267 ms
19 days agoHandshake completed267 ms
21 days agoHandshake completed340 ms
24 days agoHandshake completed269 ms
26 days agoHandshake completed283 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with m2m.monster and makes no claim about it beyond what these checks measured.