Remote MCP · Endpoint

WebinarIgnition MCP server

No. WebinarIgnition answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes 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
275 ms
Tools exposed
90 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Webinar leads and revenue from several WordPress sites, in one chat.
Listing
From the official MCP registry (active).
Recent checks of WebinarIgnition
CheckedResultHandshake
18 minutes agoHandshake completed275 ms
9 days agoHandshake completed343 ms
9 days agoHandshake completed319 ms
11 days agoHandshake completed219 ms
12 days agoHandshake completed1.09 s
13 days agoHandshake completed257 ms
14 days agoHandshake completed500 ms
14 days agoHandshake completed232 ms
16 days agoHandshake completed223 ms
19 days agoHandshake completed370 ms
21 days agoHandshake completed201 ms
24 days agoHandshake completed889 ms
26 days agoHandshake completed156 ms
28 days agoHandshake completed208 ms

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

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.