Other · Remote MCP server
WebinarIgnition
71 AI tools for WordPress webinars: 28 read-only, nothing changes without your OK.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.webinarignition/mcp- Version
- 1.0.6
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- com.webinarignition
- Namespace
- Namespace verified by the MCP Registry via the domain webinarignition.com · how
- Listed under
- WordPress MCP servers
- Website
- webinarignition.com
- Repository
- github.com/Tobias-Conrad/webinarignition-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.webinarignition.com/?src=registry | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- WebinarIgnition 1.0.7 · protocol 2025-06-18
- Tools discovered
- 2:
wi_webinar,wi_webinar_delete - Checked on
- 2026-10-05
How to connect WebinarIgnition
WebinarIgnition is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.webinarignition.com/?src=registry, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| WebAskBuild surveys, read answers and make reports in WebAsk from an AI assistant. | Remote · HTTPLive check: sign-in required |
| Webcake LandingBuild, validate, and persist Webcake landing-page source JSON: element schemas plus AI usage hints. | Remote & Local · HTTP, stdioLive check: sign-in required |
| WebeyezSession replays, JS errors, funnel drop-offs and revenue-loss diagnostics. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Webfont License AuditThe 12 licence questions a foundry audit letter asks, run against your CSS. | Local · stdio |
| WebLoom86 tools: drive YOUR real Chrome via CDP + browse/install/publish Threads in chat. webloom.run. | Local · stdio |
| WebMCP EvalEvaluate one public URL for WebMCP readiness: intent, tools observed, recommended, do-not-expose. | Remote · HTTPLive check: sign-in required |
| webPostoWebPosto ERP (management for gas stations and convenience stores) via session capture with your auth. | Remote · HTTPLive check: ✓ handshake |
| webring.onlineTraversable webring directory for the agentic web: agents, MCP servers, and agent-ready websites. | Remote · HTTPLive check: ✓ handshake |