io.usefulapi/emailoctopus
REMOTE · EMAILOCTOPUS.USEFULAPI.IO · SCANNED SEP 20
Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1364 tokens (~104/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/emailoctopus MCP server?
io.usefulapi/emailoctopus 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'
{
"mcpServers": {
"io-usefulapi-emailoctopus": {
"url": "https://emailoctopus.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-emailoctopus": {
"type": "http",
"url": "https://emailoctopus.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-emailoctopus] url = "https://emailoctopus.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-emailoctopus": {
"type": "remote",
"url": "https://emailoctopus.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-emailoctopus --url 'https://emailoctopus.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-emailoctopus:
url: "https://emailoctopus.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-emailoctopus": {
"Transport": "http",
"Url": "https://emailoctopus.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-emailoctopus -t streamable-http -u 'https://emailoctopus.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-emailoctopus": {
"type": "http",
"url": "https://emailoctopus.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Sept 26 +1
- Stability: 0.97 → pass security
- 31 Aug 26 −1
- Stability: pass → 0.93 functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 3 Aug 26 0
- Authorization: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.23 ▲ functional
- 1 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 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
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 20 Sept 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 | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 162b2d09124289a80ed13ad95e93d649 |
| SANs: usefulapi.io, emailoctopus.usefulapi.io, *.emailoctopus.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. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://emailoctopus.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://emailoctopus.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://emailoctopus.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://emailoctopus.usefulapi.io/mcp |
| Authorisation server | https://emailoctopus.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://emailoctopus.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/emailoctopus MCP server?
io.usefulapi/emailoctopus is an MCP server 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 io.usefulapi/emailoctopus MCP server safe to use?
io.usefulapi/emailoctopus scores 87 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 io.usefulapi/emailoctopus MCP server expose?
io.usefulapi/emailoctopus 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 io.usefulapi/emailoctopus MCP server require authentication?
Yes. io.usefulapi/emailoctopus asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/emailoctopus MCP server still maintained?
io.usefulapi/emailoctopus is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.