Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

WebinarIgnition

REMOTE · MCP.WEBINARIGNITION.COM · SCANNED SEP 29

Build or create a webinar from chat: registration page, invitation emails, evergreen funnel.

Available components

remote · mcp.webinarignition.com 64
64 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability68
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1896 tokens (~379/item across 5 items; 2 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the WebinarIgnition MCP server?

WebinarIgnition is a hosted endpoint at https://mcp.webinarignition.com/?src=registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.webinarignition.com

# add to Claude Code
claude mcp add --transport http com-webinarignition-mcp 'https://mcp.webinarignition.com/?src=registry'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-webinarignition-mcp": {
      "url": "https://mcp.webinarignition.com/?src=registry"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-webinarignition-mcp": {
      "type": "http",
      "url": "https://mcp.webinarignition.com/?src=registry"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-webinarignition-mcp]
url = "https://mcp.webinarignition.com/?src=registry"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-webinarignition-mcp": {
      "type": "remote",
      "url": "https://mcp.webinarignition.com/?src=registry",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-webinarignition-mcp --url 'https://mcp.webinarignition.com/?src=registry' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-webinarignition-mcp:
    url: "https://mcp.webinarignition.com/?src=registry"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-webinarignition-mcp": {
      "Transport": "http",
      "Url": "https://mcp.webinarignition.com/?src=registry"
    }
  }
}
# add to Vellum
assistant mcp add com-webinarignition-mcp -t streamable-http -u 'https://mcp.webinarignition.com/?src=registry'
// mcp.json
{
  "mcpServers": {
    "com-webinarignition-mcp": {
      "type": "http",
      "url": "https://mcp.webinarignition.com/?src=registry"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Probed https://mcp.webinarignition.com/?src=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=webinarignition.com CN=WE1,O=Google Trust Services,C=US 9 Aug 2026 7 Nov 2026 ECDSA 256 ECDSA-SHA256 77446cddafc0a21c0e43fed61ba916fa
SANs: webinarignition.com, *.webinarignition.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.webinarignition.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
webinarignition.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.webinarignition.com/?src=registry Verified 200
http (plaintext) http://mcp.webinarignition.com/?src=registry HTTPS enforced 301 https://mcp.webinarignition.com/?src=registry
MCP tools · 2 exposed · ~1,450 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
wi_webinar ~1,254

Plan, write and set up a webinar from a chat, and answer questions about WebinarIgnition. It picks a topic, produces the title, the invitation emails, the reminders and the registration page, and prepares the live, automated or evergreen room on the user's own WordPress site. Needs no sign-in. Returns JSON. `was` selects the step: • start — entry point; returns a question with tappable options. • thema — starts a conversation from the user's text; needs `text`. • weiter — continues a conversation; needs `session_id` and `text`. A result with ready=true means the texts can be written next with was=texte. • texte — writes the finished texts for a ready session; needs `session_id`. Optional: `job_id` to poll a running job, `direction` for an angle, `skip_direction`, `invite_type` (list, personal, facebook, whatsapp, instagram, linkedin, telegram, youtube), or type="custom" with `custom_channel` for any other channel. • stand — returns what the session has collected so far; needs `session_id`. • seite — checks a WordPress address for WebinarIgnition; needs `url`; returns state, next_action and next_url. • verbinden — connects the chat to the user's own WordPress; the first call needs `session_id` and `url` and returns a connect_url that the user opens in their own browser; a later call without `url` reports whether it went through. • faehigkeiten — lists the abilities of the connected site; needs `session_id`. • ausfuehren — runs one ability on the connected site; needs `session_id`, `tool` and `args`. Destructive abilities are not run here; the answer points to wi_webinar_delete. • trennen — drops the connection; needs `session_id`. • handoff — returns a handover link carrying the collected data; needs `session_id` (or `known_facts`/`content`), optional `url`. • technik — returns the setup plan without a connected site. • frage — answers a product question (prices, limits, integrations); needs `text`. • status — technical state of the connector. Returns { error, messa…

NameTypeReqDescription
argsobject–Only with was=ausfuehren: the arguments for that ability, shaped by its input_schema.
contentstring–Only with was=handoff: finished text to carry over, if the session alone does not hold it.
custom_channelstring–Only with was=texte and type="custom": the exact name of the channel or format the invitation is for when it is not one of the eight built-in platforms — e.g. Xing, WeChat, Line, KakaoTalk, Viber, Th…
directionstring–Optional with was=texte: the angle/framing of the invitation (natural language), e.g. 'Zeitersparnis und Skalierung ohne neue Mitarbeiter' for an agency. If missing, the invitation is written at once…
focusstring–Only with was=start: what it should be about.
has_mcpboolean–Only with was=start: true when the host already uses an MCP/connector — the connector normally sets this itself.
has_wiboolean–Only with was=start: true when WebinarIgnition is already installed on the host's site.
has_wordpressboolean–Only with was=start: true when the host already has a WordPress site.
invite_typestring–Only with was=texte, when the invitation is for a specific platform: list = email list, personal = personal message, facebook = Facebook post, whatsapp = WhatsApp status, instagram = Instagram post,…
job_idstring–Only with was=texte: the job number from an earlier call, to check whether the texts are ready. Without job_id a new job is started; only one text job runs at a time.
known_factsobject–Everything you already know — send it every turn so nothing is lost on a restart.
languagestring–The language the host writes in.
ratinginteger–Only with was=handoff: the host's rating (1-10), if any.
session_idstring–From an earlier turn (weiter · texte · stand).
situationstring–Only with was=start: what the host just said.
skip_directionboolean–Only with was=texte: true when the host wants NO special angle — then it generates without an angle.
textstring–What the host said (thema · weiter) or the question in the host's language (frage).
toolstring–Only with was=ausfuehren: the ability name exactly as was=faehigkeiten reported it, e.g. webinarignition_create_webinar. Slashes and hyphens are accepted too, but the site publishes underscores.
typestring–Only with was=texte: invites (default), starter, or custom. custom = the invitation is for a channel that is NOT one of the eight built-in platforms — pass the channel name in custom_channel. A chann…
urlstring–The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.
wantsarray–Only with was=start: what the host wants, as short keywords (e.g. "thema", "texte", "technik").
wasstringyesWhich step to run.
NameTypeReqDescription
result–yes–

No examples provided.

wi_webinar_delete ~196

Delete or replace something on the connected WordPress site — irreversible. Runs only an ability that is verified as destructive: delete a campaign, a webhook, registrants (single or all), the logs, the attendee questions, or the HC import that replaces a campaign. Writes abilities are not run here; use wi_webinar with was="ausfuehren" for those. Needs `session_id` and `tool`, optional `args`. Returns JSON.

NameTypeReqDescription
argsobject–The arguments for that ability, shaped by its input_schema.
session_idstringyesThe conversation id from an earlier turn — the session whose WordPress site is connected.
toolstringyesThe destructive ability name exactly as was="faehigkeiten" reported it, e.g. webinarignition_delete_campaign or webinarignition_delete_webhook. Slashes and hyphens are accepted too, but the site publ…
NameTypeReqDescription
result–yes–

No examples provided.

Common questions

What is the WebinarIgnition MCP server?

WebinarIgnition is an MCP server listed in the public MCP registry as com.webinarignition/mcp. Build or create a webinar from chat: registration page, invitation emails, evergreen funnel. This page covers its hosted endpoint (https://mcp.webinarignition.com/?src=registry).

Is the WebinarIgnition MCP server safe to use?

WebinarIgnition scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the WebinarIgnition MCP server expose?

WebinarIgnition exposes 2 tools: wi_webinar, wi_webinar_delete. Their descriptions and schemas cost roughly 1,450 tokens of context every time the server is loaded.

Does the WebinarIgnition MCP server require authentication?

No. We connected to WebinarIgnition without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the WebinarIgnition MCP server still maintained?

WebinarIgnition is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.