Remote MCP · Endpoint

io.github.gbacot-wq/omega-router MCP server

No. io.github.gbacot-wq/omega-router answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://omega-router.gbacot.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.gbacot-wq/omega-router
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
446 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Route agent services by observed price and public usage evidence.
Listing
From the official MCP registry (active).
Recent checks of io.github.gbacot-wq/omega-router
CheckedResultHandshake
1 hour agoHandshake completed446 ms
2 days agoHandshake completed320 ms
5 days agoHandshake completed204 ms
7 days agoHandshake completed181 ms
9 days agoHandshake completed318 ms
11 days agoHandshake completed81 ms
13 days agoHandshake completed232 ms
15 days agoHandshake completed153 ms
17 days agoHandshake completed179 ms
19 days agoHandshake completed140 ms
20 days agoHandshake completed82 ms
21 days agoHandshake completed153 ms
23 days agoHandshake completed250 ms
25 days agoHandshake completed189 ms

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

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 io.github.gbacot-wq/omega-router and makes no claim about it beyond what these checks measured.