Remote MCP · Endpoint

402Signal MCP server

Yes, as of 1 hour ago: the connection was refused or dropped.

DownLast checked 1 hour ago

Server URL

https://402signal.com/mcp

The last check failed: the connection was refused or dropped.

Registry name
io.github.402signal/402signal
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
47.1% from 17 checks
Described by its publisher as
Fail-closed live-endpoint x402 router. POST /route, $0.01 USDC on Base, Solana, Algorand.
Listing
From the official MCP registry (active).
Recent checks of 402Signal
CheckedResultHandshake
1 hour agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—
4 days agoFailed - the connection was refused or dropped—
5 days agoFailed - the connection was refused or dropped—
7 days agoFailed - the connection was refused or dropped—
8 days agoFailed - the connection was refused or dropped—
9 days agoFailed - the connection was refused or dropped—
12 days agoFailed - the connection was refused or dropped—
13 days agoFailed - the connection was refused or dropped—
15 days agoHandshake completed48 ms
16 days agoHandshake completed37 ms
18 days agoHandshake completed38 ms
19 days agoHandshake completed37 ms
20 days agoHandshake completed41 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed35 ms
22 days agoHandshake completed45 ms

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

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 402Signal and makes no claim about it beyond what these checks measured.