Manage email marketing campaigns, member lists and mailing results in Cyberimpact
Connect to Cyberimpact email marketing platform to read and manage members, groups, and mailing campaigns. Create mailings, add subscribers, send opt-in confirmations, and track delivery and engagement metrics.
Try asking Muse: "Show me how many people opened last week's newsletter and which links they clicked"
Source: Found in the official MCP Registry (io.usefulapi/cyberimpact) · First listed October 29, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://cyberimpact.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Cyberimpact is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://cyberimpact.usefulapi.io/mcpResponse time at the last check: 195ms. Worked in n/a of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
cyberimpact_get_accountCheck the connection and show which Cyberimpact account the API token belongs to (username, email, account name). GET /ping.cyberimpact_list_membersList subscribed contacts (members) with name, email, language, consent type, mailing counts and custom fields. status: active (in at least one group, default), orphans (in no group) or all. Filter by the date a member joined or was last updated. Bounced and unsubscribed members hcyberimpact_get_memberOne member by email address or id: all attributes, consent type, mailings received/opened/clicked and custom fields (keyed by custom field id; see cyberimpact_list_custom_fields). GET /members/{key}.cyberimpact_get_member_groupsThe groups a member belongs to (id, title, public/private, dynamic). GET /members/{key}/groups.cyberimpact_get_member_mailingsThe mailings a member received (use it to see what a contact was sent and when). GET /members/{key}/mailings.cyberimpact_get_member_consentA member's consent record: consent type, relation type, consent date, expiration and proof (for CASL compliance checks). GET /members/{key}/consent.cyberimpact_list_bounced_membersMembers whose last mailing hard-bounced (invalid addresses to clean up), with the bounce date. GET /members/bounced.cyberimpact_list_unsubscribed_membersMembers who unsubscribed, with the unsubscribe date. These contacts must not be mailed again. GET /members/unsubscribed.cyberimpact_list_custom_fieldsThe account's custom member fields (id, name, type text/date/integer/decimal). Member customFields are keyed by these ids. GET /customfields.cyberimpact_list_groupsList the account's groups (mailing lists) with member and mailing counts, public/private and dynamic flags. Use the ids to target mailings and opt-ins. GET /groups.cyberimpact_get_groupOne group by id with its member count, mailing count and flags. GET /groups/{id}.cyberimpact_list_group_membersThe members of one group, with the same member filters as cyberimpact_list_members. GET /groups/{id}/members.cyberimpact_list_mailingsList mailings by state: sent (default, archived ones excluded), scheduled (queued to go out) or archived. Each has id, subject, language, send/schedule date, recipient count and sender. Optionally only mailings sent to one group. GET /mailings/{sent|scheduled|archived}.cyberimpact_get_mailingOne mailing by id with its results: sent/delivered/stopped counts, views, clicks, delivery/click/view rates, per-link clicks, recipient groups, sender and body (HTML/text, cut at 20 000 characters). GET /mailings/{id}.cyberimpact_list_mailing_recipientsWho received a mailing and what happened: kind = all, delivered, stopped, hard_bounced, soft_bounced, unsubscribed, opened or clicked. Optionally only recipients from one group. GET /mailings/{id}/recipients[/{kind}].cyberimpact_list_templatesList the account's email templates (id, title, created/updated). GET /templates.cyberimpact_get_templateOne template by id with its HTML and text body (cut at 20 000 characters). GET /templates/{id}.cyberimpact_get_batchStatus of a bulk batch job (NEW, PROCESSING or COMPLETED) and its result. Set show_error_details to list the per-member errors. GET /batches/{id}.cyberimpact_add_memberWRITE: add a contact as a subscribed member WITHOUT a confirmation email (implied consent) and put it in the given groups; the contact can then be mailed. Only use it for people who really gave their consent (CASL); to ask the person to confirm first use cyberimpact_send_optin. Acyberimpact_update_memberWRITE: change only the given attributes of a member (other attributes stay as they are). The old values of the changed fields are overwritten and not recoverable through the API. Set new_email to change the address. PATCH /members/{key}.cyberimpact_add_member_to_groupsWRITE: add an existing member to more groups (existing group memberships are kept). Being in a group makes the member a recipient of mailings sent to it. Returns the member's groups after the update. POST /members/{key}/groups.cyberimpact_send_optinWRITE, SENDS AN EMAIL to the given address: an opt-in confirmation request. The person is added to the groups only after they confirm (the member is created if it does not exist). Use this instead of cyberimpact_add_member when you do not have the person's consent yet. Only call cyberimpact_create_groupWRITE: create a new, empty group (mailing list). A public group can be offered on subscription forms; a private one is internal. Groups cannot be deleted through this server. POST /groups.cyberimpact_create_templateWRITE: create a new email template from HTML and/or text. It is only saved in the account; nothing is sent. POST /templates.cyberimpact_create_mailingWRITE, SENDS EMAIL TO CUSTOMERS: create a mailing scheduled to be sent at send_at to every member of the chosen groups. It goes out for real unless it is cancelled in the Cyberimpact app before send_at. Only call it after the user has approved the subject, body, sender and groupshttps://cyberimpact.usefulapi.io/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Cyberimpact to help me. It is a free service with an MCP server at https://cyberimpact.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 29, 2026, 22:41 UTC) the endpoint was working, answering in 195ms. It is checked every 15 minutes.
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 25 tools, including cyberimpact_get_account, cyberimpact_list_members, cyberimpact_get_member, cyberimpact_get_member_groups. For example, you could ask Muse: "Show me how many people opened last week's newsletter and which links they clicked"
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/cyberimpact)). If you build Cyberimpact, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/cyberimpact"><img src="https://musedirectory.ai/badge/cyberimpact.svg" alt="Cyberimpact on musedirectory.ai" width="236" height="40"></a>