Name: EmailOctopus
Author: usefulapi

EmailOctopus MCP

Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.

Tool-list grade A Remote · Streamable HTTP No auth needed 13 tools v1.11.1

No reviews yet by usefulapiGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http emailoctopus-mcp https://emailoctopus.usefulapi.io/mcp

# 2 — ask your agent for something these tools do
#   emailoctopus_list_lists, emailoctopus_get_list, emailoctopus_list_contacts and 10 more

EmailOctopus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

usefulapi334 servers

24 categories

All 334 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

List all lists in the account. Returns {data:[...],paging:{...}} — each list's id, name, contact counts by status, and created_at. Paginate with limit (max 100) and starting_after (cursor from the previous page). EmailOctopus: GET /lists.

Parameter	Type	Required	Notes
limit	integer	no	Max lists to return (1..100).
starting_after	string	no	Pagination cursor — the id to start after (from the previous page's paging).

Get a single list by its id. Returns the list's full state — name, contact counts by status, and created_at. EmailOctopus: GET /lists/{list_id}.

Parameter	Type	Required	Notes
list_id	string	yes	The list's id.

List the contacts in a list. Returns {data:[...],paging:{...}} — each contact's id, email_address, fields, tags, status, and created_at. Paginate with limit (max 100) and starting_after. EmailOctopus: GET /lists/{list_id}/contacts.

Parameter	Type	Required	Notes
list_id	string	yes	The list's id.
limit	integer	no	Max contacts to return (1..100).
starting_after	string	no	Pagination cursor — the id to start after (from the previous page's paging).

Get a single contact in a list. Returns email_address, fields, tags, status, and created_at. contact_id is the MD5 hash of the lowercased email address, or the id returned by emailoctopus_list_contacts. EmailOctopus: GET /lists/{list_id}/contacts/{contact_id}.

Parameter	Type	Required	Notes
list_id	string	yes	The list's id.
contact_id	string	yes	The contact's id — the MD5 hash of the lowercased email address, or the id from list_contacts.

List all campaigns in the account. Returns {data:[...],paging:{...}} — each campaign's id, name, status, subject, and created_at. Paginate with limit (max 100) and starting_after. EmailOctopus: GET /campaigns.

Parameter	Type	Required	Notes
limit	integer	no	Max campaigns to return (1..100).
starting_after	string	no	Pagination cursor — the id to start after (from the previous page's paging).

Get a single campaign by its id. Returns the campaign's full state — name, status, subject, from, content, and created_at. EmailOctopus: GET /campaigns/{campaign_id}.

Parameter	Type	Required	Notes
campaign_id	string	yes	The campaign's id.

Get a campaign's aggregate performance report — sent, opened, clicked, bounced, unsubscribed, complained, and related counts. EmailOctopus: GET /campaigns/{campaign_id}/reports/summary.

Parameter	Type	Required	Notes
campaign_id	string	yes	The campaign's id.

Get a campaign's per-link click report — for each link in the campaign, the URL and its click counts. EmailOctopus: GET /campaigns/{campaign_id}/reports/links.

Parameter	Type	Required	Notes
campaign_id	string	yes	The campaign's id.

CREATES a new list — this MODIFIES live data. Provide a name. EmailOctopus: POST /lists. Returns the created list.

Parameter	Type	Required	Notes
name	string	yes	Human-readable name for the new list.

UPDATES an existing list by id — this MODIFIES live data. Sets the list's name. EmailOctopus: PUT /lists/{list_id}. Returns the updated list.

Parameter	Type	Required	Notes
list_id	string	yes	The list's id to update.
name	string	yes	The new name for the list.

CREATES a new contact in a list — this MODIFIES live data (adds a subscriber). email_address is required; optionally set fields (keyed by field tag), tags, and status. EmailOctopus: POST /lists/{list_id}/contacts. Returns the created contact.

Parameter	Type	Required	Notes
list_id	string	yes	The list's id to add the contact to.
email_address	string	yes	The contact's email address.
fields	object	no	Custom field values, keyed by the list's field tag (e.g. {"FirstName": "Ada"}).
tags	array	no	Tags to apply to the contact, e.g. ["vip", "beta"].
status	string	no	Subscription status: subscribed, pending, or unsubscribed.

UPDATES an existing contact in a list — this MODIFIES live data. Send only the fields you want to change (email_address, fields, tags, status). contact_id is the MD5 hash of the lowercased email address, or the id from list_contacts. EmailOctopus: PUT /lists/{list_id}/contacts/{contact_id}. Returns the updated contact.

Parameter	Type	Required	Notes
list_id	string	yes	The list's id.
contact_id	string	yes	The contact's id — the MD5 hash of the lowercased email address, or the id from list_contacts.
email_address	string	no	The contact's email address.
fields	object	no	Custom field values, keyed by the list's field tag (e.g. {"FirstName": "Ada"}).
tags	array	no	Tags to apply to the contact, e.g. ["vip", "beta"].
status	string	no	Subscription status: subscribed, pending, or unsubscribed.

PERMANENTLY REMOVES a contact from a list — this MODIFIES live data and cannot be undone. contact_id is the MD5 hash of the lowercased email address, or the id from list_contacts. EmailOctopus: DELETE /lists/{list_id}/contacts/{contact_id}.

Parameter	Type	Required	Notes
list_id	string	yes	The list's id.
contact_id	string	yes	The contact's id to delete — the MD5 hash of the lowercased email address, or the id from list_contacts.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install EmailOctopus or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.11.1 · scanned 20 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 0 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest10ff1cb5179e27b3bcafd1e2fe7df294ff7af365e130d6a65a22ae409f7e87ce

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
emailoctopus_list_lists	no tags
emailoctopus_get_list	no tags
emailoctopus_list_contacts	no tags
emailoctopus_get_contact	no tags
emailoctopus_list_campaigns	no tags
emailoctopus_get_campaign	no tags
emailoctopus_get_campaign_report	no tags
emailoctopus_get_campaign_links_report	no tags
emailoctopus_create_list	state-write	state-write: declares destructiveHint: true
emailoctopus_update_list	state-write	state-write: declares destructiveHint: true
emailoctopus_create_contact	state-write	state-write: declares destructiveHint: true
emailoctopus_update_contact	state-write	state-write: declares destructiveHint: true
emailoctopus_delete_contact	state-write	state-write: declares destructiveHint: true

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest10ff1cb5179e27b3

Scanned2026-10-20

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

EmailOctopus MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also