Remote MCP · Endpoint

StatOrigin MCP server

No. StatOrigin answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://statorigin.org/mcp

The last check completed an MCP handshake.

Registry name
org.statorigin/statorigin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
245 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Sourced industry statistics. Read-only.
Listing
From the official MCP registry (active).
Recent checks of StatOrigin
CheckedResultHandshake
20 minutes agoHandshake completed245 ms
9 days agoHandshake completed422 ms
9 days agoHandshake completed172 ms
11 days agoHandshake completed251 ms
12 days agoHandshake completed458 ms
13 days agoHandshake completed323 ms
14 days agoHandshake completed356 ms
14 days agoHandshake completed329 ms
16 days agoHandshake completed372 ms
19 days agoHandshake completed459 ms
21 days agoHandshake completed277 ms
24 days agoHandshake completed733 ms
26 days agoHandshake completed267 ms
28 days agoHandshake completed418 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 StatOrigin and makes no claim about it beyond what these checks measured.