Remote MCP · Endpoint

runx MCP server

No. runx answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://api.runx.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.runx/runx
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
The governed runtime for agent skills. Search the catalog and inspect a skill before running it.
Listing
From the official MCP registry (active).
Recent checks of runx
CheckedResultHandshake
8 hours agoHandshake completed117 ms
2 days agoHandshake completed690 ms
4 days agoHandshake completed101 ms
5 days agoHandshake completed152 ms
7 days agoHandshake completed345 ms
8 days agoHandshake completed201 ms
9 days agoHandshake completed154 ms
12 days agoHandshake completed157 ms
13 days agoHandshake completed112 ms
15 days agoHandshake completed99 ms
16 days agoHandshake completed108 ms
17 days agoHandshake completed137 ms
18 days agoHandshake completed248 ms
19 days agoHandshake completed158 ms
20 days agoHandshake completed208 ms
21 days agoHandshake completed232 ms
23 days agoHandshake completed177 ms

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

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