Remote MCP · Endpoint

paired.exchange MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://paired.exchange/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.nirholas/paired
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Launch coins quoted in tokenized stocks on Robinhood Chain; the user signs at a launch link.
Listing
From the official MCP registry (active).
Recent checks of paired.exchange
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoHandshake completed72 ms
4 days agoHandshake completed66 ms
6 days agoHandshake completed78 ms
8 days agoHandshake completed86 ms
10 days agoHandshake completed58 ms
13 days agoHandshake completed74 ms
14 days agoHandshake completed79 ms
16 days agoHandshake completed78 ms
17 days agoHandshake completed65 ms
18 days agoHandshake completed65 ms
21 days agoHandshake completed60 ms
22 days agoHandshake completed72 ms
24 days agoHandshake completed66 ms

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

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