Remote MCP · Endpoint

PARALLAX MCP server

Yes, as of 3 days ago: the hostname does not resolve.

DownLast checked 3 days ago

Server URL

https://theparallaxagent.com/mcp

The last check failed: the hostname does not resolve.

Registry name
com.theparallaxagent/parallax
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
7 tools
Uptime, last 30 days
81.8% from 11 checks
Described by its publisher as
Robinhood Chain stock tokens vs their Chainlink price: live gaps, pool depth, graded agent calls.
Listing
From the official MCP registry (active).
Recent checks of PARALLAX
CheckedResultHandshake
3 days agoFailed - the hostname does not resolve—
7 days agoFailed - the hostname does not resolve—
16 days agoHandshake completed127 ms
17 days agoHandshake completed221 ms
18 days agoHandshake completed164 ms
19 days agoHandshake completed162 ms
21 days agoHandshake completed197 ms
22 days agoHandshake completed127 ms
22 days agoHandshake completed137 ms
24 days agoHandshake completed271 ms
26 days agoHandshake completed203 ms

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

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