Remote MCP · Endpoint

ShadowGraph MCP server

Yes, as of 8 hours ago: the TLS certificate could not be verified.

DownLast checked 8 hours ago

Server URL

https://shadowalpha.online/_api/mcp

The last check failed: the TLS certificate could not be verified.

Registry name
online.shadowalpha/shadowgraph
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Live outage status, internet dependencies and pay-per-call market intelligence for AI agents.
Listing
From the official MCP registry (active).
Recent checks of ShadowGraph
CheckedResultHandshake
8 hours agoFailed - the TLS certificate could not be verified—
10 days agoHandshake completed172 ms
11 days agoHandshake completed119 ms
11 days agoHandshake completed149 ms
13 days agoHandshake completed91 ms
15 days agoHandshake completed108 ms
15 days agoHandshake completed96 ms
16 days agoHandshake completed194 ms
17 days agoHandshake completed100 ms
19 days agoHandshake completed112 ms
22 days agoHandshake completed95 ms
24 days agoHandshake completed118 ms
26 days agoHandshake completed126 ms
29 days agoHandshake completed118 ms

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

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