Remote MCP · Endpoint
EventWave MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://event-wave.base44.app/functions/eventWaveMcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.jgaethle10/eventwave
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- Event discovery and promotion workflows with human-controlled publishing and commerce.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 538 ms |
| 4 days ago | Handshake completed | 260 ms |
| 6 days ago | Handshake completed | 176 ms |
| 7 days ago | Handshake completed | 239 ms |
| 9 days ago | Handshake completed | 227 ms |
| 10 days ago | Handshake completed | 553 ms |
| 11 days ago | Handshake completed | 447 ms |
| 14 days ago | Handshake completed | 270 ms |
| 15 days ago | Handshake completed | 1.22 s |
| 17 days ago | Handshake completed | 809 ms |
| 19 days ago | Handshake completed | 192 ms |
| 20 days ago | Handshake completed | 659 ms |
| 21 days ago | Handshake completed | 541 ms |
| 22 days ago | Handshake completed | 341 ms |
| 22 days ago | Handshake completed | 206 ms |
| 23 days ago | Handshake completed | 204 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 EventWave and makes no claim about it beyond what these checks measured.