Remote MCP · Endpoint
Ray notifications MCP server
No. Ray notifications answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://ray-api.gege.mn/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.gege-mn/ray-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 591 ms
- Tools exposed
- 21 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Send email, push, Slack, Discord, Telegram and webhook notifications and manage templates with Ray.
- Website
- https://ray.gege.mn/docs
- Repository
- https://github.com/gege-mn/ray-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 591 ms |
| 2 days ago | Handshake completed | 831 ms |
| 4 days ago | Handshake completed | 604 ms |
| 5 days ago | Handshake completed | 571 ms |
| 7 days ago | Handshake completed | 605 ms |
| 8 days ago | Handshake completed | 1.11 s |
| 9 days ago | Handshake completed | 595 ms |
| 12 days ago | Handshake completed | 576 ms |
| 13 days ago | Handshake completed | 595 ms |
| 15 days ago | Handshake completed | 563 ms |
| 17 days ago | Handshake completed | 574 ms |
| 18 days ago | Handshake completed | 539 ms |
| 19 days ago | Handshake completed | 616 ms |
| 20 days ago | Handshake completed | 570 ms |
| 20 days ago | Handshake completed | 633 ms |
| 21 days ago | Handshake completed | 590 ms |
| 22 days ago | Handshake completed | 556 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 Ray notifications and makes no claim about it beyond what these checks measured.