EmailOctopus MCP by usefulapi
REMOTE · EMAILOCTOPUS.USEFULAPI.IO
Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_update_or_remove_a_subscriber” functional
- New prompt “check_how_a_campaign_did” functional
- New prompt “create_or_rename_a_list” functional
- New prompt “find_which_links_got_the_most_clicks” functional
- New prompt “see_how_many_subscribers_each_list_has” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://emailoctopus.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of emailoctopus.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://emailoctopus.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/emailoctopus/ |
| http (plaintext) | http://emailoctopus.usefulapi.io/mcp | Inconclusive | 302 | http://emailoctopus.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
emailoctopus_create_contact Create contact ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| email_address | string | yes | The contact's email address. |
| fields | object | – | Custom field values, keyed by the list's field tag (e.g. {"FirstName": "Ada"}). |
| list_id | string | yes | The list's id to add the contact to. |
| status | string | – | Subscription status: subscribed, pending, or unsubscribed. |
| tags | array | – | Tags to apply to the contact, e.g. ["vip", "beta"]. |
No output schema declared.
No examples provided.
emailoctopus_create_list Create list ~56
CREATES a new list — this MODIFIES live data. Provide a `name`. EmailOctopus: POST /lists. Returns the created list.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Human-readable name for the new list. |
No output schema declared.
No examples provided.
emailoctopus_delete_contact Delete contact ~120
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact's id to delete — the MD5 hash of the lowercased email address, or the id from list_contacts. |
| list_id | string | yes | The list's id. |
No output schema declared.
No examples provided.
emailoctopus_get_campaign Get campaign ~64
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign's id. |
No output schema declared.
No examples provided.
emailoctopus_get_campaign_links_report Get campaign links report ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign's id. |
No output schema declared.
No examples provided.
emailoctopus_get_campaign_report Get campaign report ~65
Get a campaign's aggregate performance report — sent, opened, clicked, bounced, unsubscribed, complained, and related counts. EmailOctopus: GET /campaigns/{campaign_id}/reports/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign's id. |
No output schema declared.
No examples provided.
emailoctopus_get_contact Get contact ~122
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact's id — the MD5 hash of the lowercased email address, or the id from list_contacts. |
| list_id | string | yes | The list's id. |
No output schema declared.
No examples provided.
emailoctopus_get_list Get list ~60
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list's id. |
No output schema declared.
No examples provided.
emailoctopus_list_campaigns List campaigns ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max campaigns to return (1..100). |
| starting_after | string | – | Pagination cursor — the id to start after (from the previous page's paging). |
No output schema declared.
No examples provided.
emailoctopus_list_contacts List contacts ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max contacts to return (1..100). |
| list_id | string | yes | The list's id. |
| starting_after | string | – | Pagination cursor — the id to start after (from the previous page's paging). |
No output schema declared.
No examples provided.
emailoctopus_list_lists List lists ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max lists to return (1..100). |
| starting_after | string | – | Pagination cursor — the id to start after (from the previous page's paging). |
No output schema declared.
No examples provided.
emailoctopus_update_contact Update contact ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | The contact's email address. |
| fields | object | – | Custom field values, keyed by the list's field tag (e.g. {"FirstName": "Ada"}). |
| list_id | string | yes | The list's id. |
| status | string | – | Subscription status: subscribed, pending, or unsubscribed. |
| tags | array | – | Tags to apply to the contact, e.g. ["vip", "beta"]. |
No output schema declared.
No examples provided.
emailoctopus_update_list Update list ~76
UPDATES an existing list by id — this MODIFIES live data. Sets the list's `name`. EmailOctopus: PUT /lists/{list_id}. Returns the updated list.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list's id to update. |
| name | string | yes | The new name for the list. |
No output schema declared.
No examples provided.
How do I install the EmailOctopus MCP by usefulapi server?
EmailOctopus MCP by usefulapi is a hosted endpoint at https://emailoctopus.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · emailoctopus.usefulapi.io
claude mcp add --transport http io-usefulapi-emailoctopus 'https://emailoctopus.usefulapi.io/mcp'
What is the EmailOctopus MCP by usefulapi server?
EmailOctopus MCP by usefulapi is listed in the public MCP registry as io.usefulapi/emailoctopus. Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus. This page covers its hosted endpoint (https://emailoctopus.usefulapi.io/mcp).
Is the EmailOctopus MCP by usefulapi server safe to use?
EmailOctopus MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EmailOctopus MCP by usefulapi server expose?
EmailOctopus MCP by usefulapi exposes 13 tools: emailoctopus_list_lists, emailoctopus_get_list, emailoctopus_list_contacts, emailoctopus_get_contact, emailoctopus_list_campaigns, and 8 more. Their descriptions and schemas cost roughly 1,364 tokens of context every time the server is loaded.
Does the EmailOctopus MCP by usefulapi server require authentication?
Its publisher declares no required credentials for EmailOctopus MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the EmailOctopus MCP by usefulapi server still maintained?
EmailOctopus MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EmailOctopus MCP by usefulapi server?
VerifyMCP ran 4 checks on EmailOctopus MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about EmailOctopus MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.