Remote MCP · Endpoint
WebinarIgnition MCP server
No. WebinarIgnition answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.webinarignition.com/
The last check completed an MCP handshake.
- Registry name
- com.webinarignition/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 225 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 16 checks
- Described by its publisher as
- Build or create a webinar from chat: registration page, invitation emails, evergreen funnel.
- Website
- https://webinarignition.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 225 ms |
| 2 days ago | Handshake completed | 176 ms |
| 4 days ago | Handshake completed | 155 ms |
| 6 days ago | Handshake completed | 151 ms |
| 7 days ago | Handshake completed | 211 ms |
| 9 days ago | Handshake completed | 154 ms |
| 10 days ago | Handshake completed | 160 ms |
| 11 days ago | Handshake completed | 239 ms |
| 14 days ago | Handshake completed | 149 ms |
| 15 days ago | Handshake completed | 158 ms |
| 17 days ago | Handshake completed | 232 ms |
| 18 days ago | Handshake completed | 143 ms |
| 19 days ago | Handshake completed | 151 ms |
| 20 days ago | Handshake completed | 164 ms |
| 21 days ago | Handshake completed | 144 ms |
| 22 days ago | Handshake completed | 221 ms |
The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.
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 WebinarIgnition and makes no claim about it beyond what these checks measured.