# io.usefulapi/emailoctopus (remote · emailoctopus.usefulapi.io)

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

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `emailoctopus.usefulapi.io`: 74/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-emailoctopus/emailoctopus.md), [page](https://verifymcp.io/servers/io-usefulapi-emailoctopus/emailoctopus)

## Channel facts

- Endpoint: `https://emailoctopus.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1364 tokens (~104/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-emailoctopus https://emailoctopus.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-emailoctopus]
url = "https://emailoctopus.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-emailoctopus": {
      "type": "remote",
      "url": "https://emailoctopus.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-emailoctopus --url https://emailoctopus.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-emailoctopus:
    url: "https://emailoctopus.usefulapi.io/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 74, +46)

- [security improvement] Authorization: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Tool coverage: unverified → 100

### 2026-08-01 (score 28, −44)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 72, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 70, +58)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 12)

First indexed and scored.

## MCP tools (13)

### `emailoctopus_list_lists` (~114 tokens)

List lists

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.

Input parameters:

- `limit` (integer): Max lists to return (1..100).
- `starting_after` (string): Pagination cursor — the id to start after (from the previous page's paging).

### `emailoctopus_get_list` (~60 tokens)

Get list

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}.

Input parameters:

- `list_id` (string, required): The list's id.

### `emailoctopus_list_contacts` (~126 tokens)

List contacts

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.

Input parameters:

- `limit` (integer): Max contacts to return (1..100).
- `list_id` (string, required): The list's id.
- `starting_after` (string): Pagination cursor — the id to start after (from the previous page's paging).

### `emailoctopus_get_contact` (~122 tokens)

Get contact

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}.

Input parameters:

- `contact_id` (string, required): The contact's id — the MD5 hash of the lowercased email address, or the id from list_contacts.
- `list_id` (string, required): The list's id.

### `emailoctopus_list_campaigns` (~108 tokens)

List campaigns

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.

Input parameters:

- `limit` (integer): Max campaigns to return (1..100).
- `starting_after` (string): Pagination cursor — the id to start after (from the previous page's paging).

### `emailoctopus_get_campaign` (~64 tokens)

Get campaign

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}.

Input parameters:

- `campaign_id` (string, required): The campaign's id.

### `emailoctopus_get_campaign_report` (~65 tokens)

Get campaign report

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

Input parameters:

- `campaign_id` (string, required): The campaign's id.

### `emailoctopus_get_campaign_links_report` (~64 tokens)

Get campaign links report

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.

Input parameters:

- `campaign_id` (string, required): The campaign's id.

### `emailoctopus_create_list` (~56 tokens)

Create list

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

Input parameters:

- `name` (string, required): Human-readable name for the new list.

### `emailoctopus_update_list` (~76 tokens)

Update 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.

Input parameters:

- `list_id` (string, required): The list's id to update.
- `name` (string, required): The new name for the list.

### `emailoctopus_create_contact` (~174 tokens)

Create contact

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.

Input parameters:

- `email_address` (string, required): The contact's email address.
- `fields` (object): Custom field values, keyed by the list's field tag (e.g. {"FirstName": "Ada"}).
- `list_id` (string, required): 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"].

### `emailoctopus_update_contact` (~215 tokens)

Update contact

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.

Input parameters:

- `contact_id` (string, required): 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, required): The list's id.
- `status` (string): Subscription status: subscribed, pending, or unsubscribed.
- `tags` (array): Tags to apply to the contact, e.g. ["vip", "beta"].

### `emailoctopus_delete_contact` (~120 tokens)

Delete contact

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}.

Input parameters:

- `contact_id` (string, required): The contact's id to delete — the MD5 hash of the lowercased email address, or the id from list_contacts.
- `list_id` (string, required): The list's id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-emailoctopus/emailoctopus#diagnostics

## Score history

- 2026-08-03: 74
- 2026-08-02: 28
- 2026-08-01: 28
- 2026-07-31: 72
- 2026-07-30: 70
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 12

## Links

- Remote endpoint: https://emailoctopus.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-emailoctopus/emailoctopus/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-emailoctopus/emailoctopus/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-emailoctopus/emailoctopus