accueil / serveurs / Recherche & Web / com.webinarignition/mcp
com.webinarignition/mcp
serveur MCP (Model Context Protocol) · WebinarIgnition 1.8.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.webinarignition/mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.webinarignition/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 18 outils
- wi_answer_product_question≈ 275 tokens
Answers a question about WebinarIgnition — price, limits, integrations, whether it fits — from the connector's verified knowledge base. Read-only: no session is created, no site is touched, nothing is changed. The answer comes only from that base: when it holds no matching entry, the response says so and carries the canonical product address https://webinarignition.com/.
Paramètres, retour & exemple (2)
Paramètrestext· string · optionnel
What the host said (thema · weiter) or the question in the host's language (frage).language· string · optionnel
The language the host writes in.
Exemple d'appel{"name": "wi_answer_product_question", "arguments": {"text": "texte", "language": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_check_wordpress≈ 210 tokens
Checks whether a WordPress address runs WebinarIgnition and in which state: not installed, installed but too old, or ready. Side effect: none — it reads the address over HTTPS and changes nothing. Needs `url`.
Paramètres, retour & exemple (1)
Paramètresurl· string · optionnel
The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.
Exemple d'appel{"name": "wi_check_wordpress", "arguments": {"url": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_connect_wordpress_woocommerce_site≈ 252 tokens
Connects this chat to the host's own WordPress site. Side effect: it creates a connect link that the host must open and approve in their own browser — until they do, nothing is connected; no password is seen or stored. Needs `session_id` and `url`.
Paramètres, retour & exemple (2)
Paramètresurl· string · optionnel
The WordPress address (seite). With was=handoff: the host's WordPress address to point the handover link at.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_connect_wordpress_woocommerce_site", "arguments": {"url": "texte", "session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_continue_webinar≈ 623 tokens
Continues an open webinar conversation by exactly one turn: pass what the host said as `text` and get the reply with the next tappable choices. Side effect: the answer is stored in the conversation state (facts, flow position) for `session_id`; nothing is written to a WordPress site and nothing is sent to anyone. Needs `session_id` and `text`. The reply carries `flow` ({ jetzt, weiter, auch, chips }) with the next choices; on the next call the open `flow.jetzt` goes into `flow_step` and the chosen chip's label into `flow_choice`. A reply with ready=true means the texts can be written next with `wi_write_webinar_invitation_emails`.
Paramètres, retour & exemple (7)
Paramètrestext· string · optionnel
What the host said (thema · weiter) or the question in the host's language (frage).language· string · optionnel
The language the host writes in.flow_step· string · optionnel
the flow step that was open in the previous answer — copy it from the returned `flow.jetzt`. It tells the server where the conversation stands so it does not have to guess.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).flow_choice· string · optionnel
which chip the host tapped, EXACTLY as its label read in the returned `flow.chips` (or the label of an own option). The server advances the flow from this.known_facts· object · optionnel
Everything you already know — send it every turn so nothing is lost on a restart. On the FIRST call (this call or this call) this is how a chat/assistant hands over what it already learned about the host (topic, audience, offer, style/tone) instead of making them repeat it.flow_strecke· string · optionnel
the route (Strecke) that runs — copy it from the returned `flow.strecke`. It tells the server which route to follow so it does not fall back to the default.
Exemple d'appel{"name": "wi_continue_webinar", "arguments": {"text": "texte", "language": "texte", "flow_step": "texte", "session_id": "texte", "flow_choice": "texte", "known_facts": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_create_handoff_link≈ 328 tokens
Returns a link that carries everything collected so far into the WebinarIgnition dashboard, so the host can finish there. Side effect: it only creates a link with the session data in it; nothing is written to a WordPress site and nothing is sent to anyone. Needs `session_id` (or `content`), optional `url` and `rating`.
Paramètres, retour & exemple (4)
Paramètresurl· string · optionnel
The WordPress address (seite). With this call: the host's WordPress address to point the handover link at.rating· integer · optionnel
the host's rating (1-10), if any.content· string · optionnel
finished text to carry over, if the session alone does not hold it.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_create_handoff_link", "arguments": {"url": "texte", "rating": 1, "content": "texte", "session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_create_webinar_registration_page≈ 316 tokens
Builds the webinar on the connected WordPress site: it creates the campaign with the facts the session has collected — title, date, room type — and returns the registration and room links. Side effect: it creates real content on the host's site: a campaign with its registration page and its room. Needs `session_id`. Optional `args` overrides single fields (e.g. a different `start_date`).
Paramètres, retour & exemple (3)
Paramètresargs· object · optionnel
the arguments for that ability, shaped by its input_schema.language· string · optionnel
The language the host writes in.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_create_webinar_registration_page", "arguments": {"args": {}, "language": "texte", "session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_delete_webinar≈ 252 tokens
Deletes the webinar that belongs to this session from the connected WordPress site — irreversible, it cannot be undone: the campaign and everything attached to it are gone. Needs `session_id`; optional `args` names the campaign when the session holds more than one.
Paramètres, retour & exemple (2)
Paramètresargs· object · optionnel
the arguments for that ability, shaped by its input_schema.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_delete_webinar", "arguments": {"args": {}, "session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_disconnect_wordpress≈ 211 tokens
Drops the stored connection between this chat and the host's WordPress site. Material loss / hard to reverse: the connection has to be approved again in the host's own browser before anything else can run. The site itself stays untouched. Needs `session_id`.
Paramètres, retour & exemple (1)
Paramètressession_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_disconnect_wordpress", "arguments": {"session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_get_connector_status≈ 170 tokens
Reads the technical state of the WebinarIgnition connector: version, protocol, which WordPress site is connected, whether the connection is healthy. Read-only, needs no input and changes nothing.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "wi_get_connector_status", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_get_session_facts≈ 216 tokens
Reads what the current webinar session has collected so far — topic, audience, date, texts state. Read-only: no session is created, no site is touched, nothing is written. The session already holds what it was told, so nothing in it has to be asked again. Needs `session_id`.
Paramètres, retour & exemple (1)
Paramètressession_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_get_session_facts", "arguments": {"session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_get_setup_plan≈ 224 tokens
Returns the step-by-step setup plan for the host's WordPress site — what has to be installed, what to click, what the room needs — without touching the site. Read-only. Optional `session_id` adds what the session already knows.
Paramètres, retour & exemple (2)
Paramètreslanguage· string · optionnel
The language the host writes in.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_get_setup_plan", "arguments": {"language": "texte", "session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_get_webinar_attendance_stats≈ 374 tokens
Reads how many people registered, how many came live, how many stayed long enough to see the offer and how many watched the replay — with the show-up rate. Read-only, changes nothing. Use it when the host asks how many showed up, what the show-up rate is, whether the reminders worked, or who watched the replay. Do not use it for money or per-person data. Rates are only reported when at least 20 people were in the earlier step; below that the answer says so instead of inventing a percentage. Without a connected site the answer carries example numbers (sample: true) and the next step.
Paramètres, retour & exemple (3)
Paramètresutm· string · optionnel
Filter the numbers by one UTM value, e.g. a source such as facebook.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).webinar_id· integer · optionnel
The webinar (campaign) id. Leave it out when the session already built one.
Exemple d'appel{"name": "wi_get_webinar_attendance_stats", "arguments": {"utm": "texte", "session_id": "texte", "webinar_id": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_get_webinar_funnel_conversion_stats≈ 456 tokens
Reads the whole funnel of a webinar — unique visitors, registrations, live attendance, watched enough, offer shown, offer clicked, replay, purchased — with the step-to-step conversion rates, a ranking across the host's webinars and one sentence saying which step to fix first. Read-only, changes nothing. Use it when the host asks how the funnel converts, where people drop off, how the webinar compares to the others, or what to improve. Do not use it for single registrants (that is wi_list_webinar_leads_registrants) or for money in currency (that is wi_get_webinar_revenue_woocommerce). Rates need at least 20 people in the earlier step, otherwise the answer says 'not enough data' instead of a percentage. Without a connected site the answer carries example numbers (sample: true) and the next step.
Paramètres, retour & exemple (4)
Paramètresall· boolean · optionnel
true compares all webinars and ranks them by volume.utm· string · optionnel
Filter the whole funnel by one UTM value, e.g. a source such as facebook.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).webinar_id· integer · optionnel
The webinar (campaign) id. Leave it out to rank all webinars of the host.
Exemple d'appel{"name": "wi_get_webinar_funnel_conversion_stats", "arguments": {"all": true, "utm": "texte", "session_id": "texte", "webinar_id": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_get_webinar_revenue_woocommerce≈ 362 tokens
Reads what a webinar earned: paid orders and the amount per currency, open orders, refunds — and which offer tier (product) sold how often and for how much. Read-only, changes nothing. Money comes from the host's own shop (WooCommerce or any other shop connected to the site), never from estimates. Use it when the host asks what the webinar earned, which package sold, or where the upsell from tier to tier breaks. Do not use it for per-person spending (that is wi_list_webinar_leads_registrants) and never add two currencies together — each line stays separate. Without a connected site the answer carries example numbers (sample: true) and the next step.
Paramètres, retour & exemple (2)
Paramètressession_id· string · optionnel
From an earlier turn (weiter · texte · stand).webinar_id· integer · optionnel
The webinar (campaign) id. Leave it out to read all webinars.
Exemple d'appel{"name": "wi_get_webinar_revenue_woocommerce", "arguments": {"session_id": "texte", "webinar_id": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_list_site_abilities≈ 203 tokens
Lists the abilities the connected WordPress site offers, with their arguments and whether they are read-only, write or destructive. Read-only: it reads a list from the site and changes nothing. Needs `session_id`.
Paramètres, retour & exemple (1)
Paramètressession_id· string · optionnel
From an earlier turn (weiter · texte · stand).
Exemple d'appel{"name": "wi_list_site_abilities", "arguments": {"session_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_list_webinar_leads_registrants≈ 492 tokens
Reads the registrant list of one webinar from the host's own WordPress site: name, email, signup time, attended, watched replay, purchased, UTM source, and what each registrant spent when the shop provides it. Read-only, it changes nothing. Use it when the host asks who registered, how many leads came in, whom to follow up, or what a single lead bought. Do not use it for aggregate numbers (that is wi_get_webinar_funnel_conversion_stats), for deleting data, or for exporting a file. Personal data stays where it belongs: the tool reads only the site this chat is connected to, the site the host approved, and never another site. It returns personal data only when the host's licence includes the registrant export (export_leads). Without that licence the site answers with the code license_required and an upgrade link, and no personal data is returned. Without a connected site the answer carries clearly marked example numbers (sample: true) from a static demo file that contains no real person, plus the next step.
Paramètres, retour & exemple (3)
Paramètreslimit· integer · optionnel
How many registrants to return, 1-200. Default 50.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).webinar_id· integer · optionnel
The webinar (campaign) id. Leave it out when the session already built one.
Exemple d'appel{"name": "wi_list_webinar_leads_registrants", "arguments": {"limit": 1, "session_id": "texte", "webinar_id": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_start_webinar≈ 579 tokens
Starts a new webinar in WebinarIgnition and returns the first question with tappable options — no sign-in, no setup. Side effect: it creates a new webinar session on the connector and returns a `session_id`; nothing is written to a WordPress site, nothing is published and no email is sent. `situation` takes the host's own words, `known_facts` what is already known (topic, audience, offer, tone); with either, the conversation opens at that point instead of an empty menu. The reply carries a `session_id` for `wi_continue_webinar`.
Paramètres, retour & exemple (6)
Paramètresfocus· string · optionnel · thema | texte | technik | fragen | alles
what it should be about.has_wi· boolean · optionnel
true when WebinarIgnition is already installed on the host's site.language· string · optionnel
The language the host writes in.situation· string · optionnel
Only with this call or this call: what the host just said, in their own words. On this call this also starts a real conversation (seeded with known_facts) instead of only showing the menu — use it when the host already wrote something about their webinar.known_facts· object · optionnel
Everything you already know — send it every turn so nothing is lost on a restart. On the FIRST call (this call or this call) this is how a chat/assistant hands over what it already learned about the host (topic, audience, offer, style/tone) instead of making them repeat it.has_wordpress· boolean · optionnel
true when the host already has a WordPress site. Reist als Fluss-Signal mit: ohne es gilt der Standardweg (der Host hat vermutlich WordPress). Mit false wird der Verbinden-Schritt in der Strecke uebersprungen.
Exemple d'appel{"name": "wi_start_webinar", "arguments": {"focus": "thema", "has_wi": true, "language": "texte", "situation": "texte", "known_facts": {}, "has_wordpress": true}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}} - wi_write_webinar_invitation_emails≈ 760 tokens
Writes the finished webinar texts for a session that is ready: title, invitation email, reminders and the registration copy. Side effect: it starts a text-generation job on the connector (about a minute) and stores the result in the session; nothing is published to a WordPress site and no email is sent to anyone. Needs `session_id`. A second call with the returned `job_id` reads the job's state until the texts are there. Optional: `invite_type` for one of the eight built-in channels, `type="custom"` with `custom_channel` for any other channel, `direction` for an angle or `skip_direction` for none.
Paramètres, retour & exemple (8)
Paramètrestype· string · optionnel
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 channel outside the eight built-ins is written as custom, not as one of the eight.job_id· string · optionnel
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.language· string · optionnel
The language the host writes in.direction· string · optionnel
Optional with this call: 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 without a special angle.session_id· string · optionnel
From an earlier turn (weiter · texte · stand).invite_type· string · optionnel · list | personal | facebook | whatsapp | instagram | linkedin | telegram | youtube
Only with this call, when the invitation is for a specific platform: list = email list, personal = personal message, facebook = Facebook post, whatsapp = WhatsApp status, instagram = Instagram post, linkedin = LinkedIn post, telegram = Telegram channel, youtube = YouTube post.custom_channel· string · optionnel
Only with this call 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, Threads, Mastodon, a guest article, or the host's own format. The text is then written for exactly this channel, not for a built-in platform.skip_direction· boolean · optionnel
true when the host wants NO special angle — then it generates without an angle.
Exemple d'appel{"name": "wi_write_webinar_invitation_emails", "arguments": {"type": "texte", "job_id": "texte", "language": "texte", "direction": "texte", "session_id": "texte", "invite_type": "list"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».