Remote MCP · Endpoint
Ray notifications MCP server
No. Ray notifications answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 725 ms
- Tools exposed
- 21 tools
- Uptime, last 30 days
- 100% from 18 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 |
|---|---|---|
| 1 hour ago | Handshake completed | 725 ms |
| 1 day ago | Handshake completed | 756 ms |
| 2 days ago | Handshake completed | 793 ms |
| 3 days ago | Handshake completed | 770 ms |
| 4 days ago | Handshake completed | 755 ms |
| 5 days ago | Handshake completed | 764 ms |
| 6 days ago | Handshake completed | 748 ms |
| 9 days ago | Handshake completed | 810 ms |
| 11 days ago | Handshake completed | 242 ms |
| 14 days ago | Handshake completed | 835 ms |
| 16 days ago | Handshake completed | 806 ms |
| 18 days ago | Handshake completed | 650 ms |
| 20 days ago | Handshake completed | 591 ms |
| 22 days ago | Handshake completed | 831 ms |
| 24 days ago | Handshake completed | 604 ms |
| 26 days ago | Handshake completed | 571 ms |
| 27 days ago | Handshake completed | 605 ms |
| 29 days ago | Handshake completed | 1.11 s |
The last 18 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.
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.