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/?src=registry

The last check completed an MCP handshake.

Registry name
com.webinarignition/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
889 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Webinar leads, registrants and revenue from WordPress and WooCommerce, in the chat.
Listing
From the official MCP registry (active).
Recent checks of WebinarIgnition
CheckedResultHandshake
2 hours agoHandshake completed889 ms
2 days agoHandshake completed156 ms
4 days agoHandshake completed208 ms
6 days agoHandshake completed200 ms
8 days agoHandshake completed444 ms
10 days agoHandshake completed147 ms
11 days agoHandshake completed165 ms
13 days agoHandshake completed148 ms
14 days agoHandshake completed316 ms
15 days agoHandshake completed267 ms
18 days agoHandshake completed140 ms
19 days agoHandshake completed272 ms
21 days agoHandshake completed170 ms
23 days agoHandshake completed183 ms
24 days agoHandshake completed145 ms

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

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.