# Cyberimpact Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Cyberimpact

Manage email marketing campaigns, member lists and mailing results in Cyberimpact

- Record: https://musedirectory.ai/connector/cyberimpact
- Category: Marketing & Ads
- Developer: usefulapi (https://usefulapi.io/cyberimpact/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 195ms, checked 2026-10-29T22:41:10Z
- Endpoint: https://cyberimpact.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T22:41:10Z)
- Source: Found in the official MCP Registry (io.usefulapi/cyberimpact) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fcyberimpact

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.

Example request: "Show me how many people opened last week's newsletter and which links they clicked"

How to connect: Not 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.

Tools:
- cyberimpact_get_account: Check the connection and show which Cyberimpact account the API token belongs to (username, email, account name). GET /ping.
- cyberimpact_list_members: List 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 h
- cyberimpact_get_member: One 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_groups: The groups a member belongs to (id, title, public/private, dynamic). GET /members/{key}/groups.
- cyberimpact_get_member_mailings: The mailings a member received (use it to see what a contact was sent and when). GET /members/{key}/mailings.
- cyberimpact_get_member_consent: A member's consent record: consent type, relation type, consent date, expiration and proof (for CASL compliance checks). GET /members/{key}/consent.
- cyberimpact_list_bounced_members: Members whose last mailing hard-bounced (invalid addresses to clean up), with the bounce date. GET /members/bounced.
- cyberimpact_list_unsubscribed_members: Members who unsubscribed, with the unsubscribe date. These contacts must not be mailed again. GET /members/unsubscribed.
- cyberimpact_list_custom_fields: The account's custom member fields (id, name, type text/date/integer/decimal). Member customFields are keyed by these ids. GET /customfields.
- cyberimpact_list_groups: List 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_group: One group by id with its member count, mailing count and flags. GET /groups/{id}.
- cyberimpact_list_group_members: The members of one group, with the same member filters as cyberimpact_list_members. GET /groups/{id}/members.
- cyberimpact_list_mailings: List 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_mailing: One 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_recipients: Who 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_templates: List the account's email templates (id, title, created/updated). GET /templates.
- cyberimpact_get_template: One template by id with its HTML and text body (cut at 20 000 characters). GET /templates/{id}.
- cyberimpact_get_batch: Status 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_member: WRITE: 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. A
- cyberimpact_update_member: WRITE: 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_groups: WRITE: 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_optin: WRITE, 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_group: WRITE: 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_template: WRITE: create a new email template from HTML and/or text. It is only saved in the account; nothing is sent. POST /templates.
- cyberimpact_create_mailing: WRITE, 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 groups

Screening checks:
- MCP handshake: pass (Answered in 195ms)
- Domain against threat feeds (Cloudflare security DNS): pass (cyberimpact.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (25 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)