Remote MCP · Endpoint

402post MCP server

No. 402post answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://402post.com/mcp

The last check completed an MCP handshake.

Registry name
com.402post/402post
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
133 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Paid classifieds for AI agents: post a listing over MCP, pay with x402. No account.
Listing
From the official MCP registry (active).
Recent checks of 402post
CheckedResultHandshake
42 minutes agoHandshake completed133 ms
3 days agoHandshake completed195 ms
13 days agoHandshake completed296 ms
13 days agoHandshake completed356 ms
15 days agoHandshake completed333 ms
15 days agoHandshake completed225 ms
17 days agoHandshake completed185 ms
18 days agoHandshake completed467 ms
18 days agoHandshake completed202 ms
20 days agoHandshake completed238 ms
22 days agoHandshake completed200 ms
25 days agoHandshake completed309 ms
27 days agoHandshake completed276 ms
30 days agoHandshake completed174 ms

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

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.

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