Remote MCP · Endpoint

works.relux/agent-gateway MCP server

No. works.relux/agent-gateway answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.relux.works/mcp

The last check completed an MCP handshake.

Registry name
works.relux/agent-gateway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Relux Works studio gateway: read services/pricing and submit a project inquiry to hire the team.
Website
https://relux.works/
Listing
From the official MCP registry (active).
Recent checks of works.relux/agent-gateway
CheckedResultHandshake
1 hour agoHandshake completed66 ms
1 day agoHandshake completed51 ms
2 days agoHandshake completed100 ms
3 days agoHandshake completed69 ms
4 days agoHandshake completed52 ms
5 days agoHandshake completed52 ms
6 days agoHandshake completed85 ms
8 days agoHandshake completed67 ms
11 days agoHandshake completed52 ms
13 days agoHandshake completed68 ms
15 days agoHandshake completed65 ms
18 days agoHandshake completed61 ms
20 days agoHandshake completed65 ms
22 days agoHandshake completed50 ms
24 days agoHandshake completed124 ms
26 days agoHandshake completed41 ms
27 days agoHandshake completed48 ms
29 days agoHandshake completed60 ms
29 days agoHandshake completed43 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with works.relux/agent-gateway and makes no claim about it beyond what these checks measured.