Remote MCP · Endpoint

OrionCMD Checks MCP server

No. OrionCMD Checks answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.orioncmd.com/mcp

The last check completed an MCP handshake.

Registry name
com.orioncmd.api/checks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
466 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Domain threat checks, a 30-day domain watch, TLS/DNS/email-auth checks and a $2 site audit (x402).
Listing
From the official MCP registry (active).
Recent checks of OrionCMD Checks
CheckedResultHandshake
2 hours agoHandshake completed466 ms
1 day agoHandshake completed218 ms
2 days agoHandshake completed360 ms
3 days agoHandshake completed338 ms
4 days agoHandshake completed231 ms
5 days agoHandshake completed481 ms
7 days agoHandshake completed296 ms
10 days agoHandshake completed281 ms
12 days agoHandshake completed96 ms
14 days agoHandshake completed240 ms
17 days agoHandshake completed382 ms
19 days agoHandshake completed331 ms
21 days agoHandshake completed253 ms
23 days agoHandshake completed223 ms
25 days agoHandshake completed314 ms

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

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