Cyberimpact MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://cyberimpact.usefulapi.io/mcp

claude mcp add --transport http cyberimpact https://cyberimpact.usefulapi.io/mcp

{
  "mcpServers": {
    "cyberimpact": {
      "url": "https://cyberimpact.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "cyberimpact": {
      "type": "http",
      "url": "https://cyberimpact.usefulapi.io/mcp"
    }
  }
}

https://cyberimpact.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 33 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 25 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32417 servers in this category
• Published to the registry more recently than 97% of the other 32417 servers in this category
• Basic checks equal to or better than 100% of the other 32417 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{