# rapidmail MCP by usefulapi (remote · rapidmail.usefulapi.io)

Read rapidmail lists, recipients, mailings and stats; add, update or unsubscribe one recipient.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://rapidmail.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-17.

- **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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2518 tokens (~157/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the rapidmail MCP by usefulapi server?

rapidmail MCP by usefulapi is a hosted endpoint at https://rapidmail.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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-rapidmail": {
      "url": "https://rapidmail.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-rapidmail": {
      "type": "http",
      "url": "https://rapidmail.usefulapi.io/mcp"
    }
  }
}
```

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-rapidmail": {
      "Transport": "http",
      "Url": "https://rapidmail.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-rapidmail -t streamable-http -u 'https://rapidmail.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-rapidmail": {
      "type": "http",
      "url": "https://rapidmail.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-10-16 (score 64, +1)

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

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (16)

### `rapidmail_list_recipientlists` (~85 tokens)

List recipient lists

List the recipient lists (newsletter audiences) of the rapidmail account with id, name, description, whether unsubscribed recipients are blacklisted, and which is the default. Use the ids for recipients and mailing filters. GET /recipientlists.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `rapidmail_get_recipientlist` (~39 tokens)

Get recipient list

One recipient list by id. GET /recipientlists/{id}.

Input parameters:

- `recipientlist_id` (integer, required): rapidmail recipient list id.

### `rapidmail_get_recipientlist_activity_stats` (~111 tokens)

Get recipient list activity stats

Subscription activity of one recipient list between two dates (for example new subscriptions and unsubscriptions). The range may be at most one year, must not start before the list was created and must not lie in the future. GET /recipientlists/{id}/stats/activity.

Input parameters:

- `from` (string, required): Start date, yyyy-mm-dd.
- `recipientlist_id` (integer, required): rapidmail recipient list id.
- `to` (string, required): End date, yyyy-mm-dd; later than from.

### `rapidmail_list_recipients` (~216 tokens)

List recipients

List the recipients (subscribers) of ONE recipient list, optionally filtered by e-mail address, external id or status. recipientlist_id is required. The long text fields (extrabig1-10) are only returned with include_extrabig. GET /recipients.

Input parameters:

- `email` (string): Only the recipient with this e-mail address.
- `foreign_id` (string): Only the recipient with this external id.
- `include_extrabig` (boolean): Also return the long text fields extrabig1-10 (default false).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `recipientlist_id` (integer, required): rapidmail recipient list id (see rapidmail_list_recipientlists).
- `sort_by` (string): Sort field.
- `sort_order` (string): Sort direction.
- `status` (array): Only recipients in these statuses: new (awaiting confirmation), active, bounced, abused, deleted.

### `rapidmail_get_recipient` (~47 tokens)

Get recipient

One recipient by id: e-mail, name, status, custom fields and timestamps. GET /recipients/{id}.

Input parameters:

- `recipient_id` (integer, required): rapidmail recipient id.

### `rapidmail_create_recipient` (~496 tokens)

Add recipient

WRITE: add ONE recipient (subscriber) to a recipient list. By default double opt-in is used: the recipient is created with status 'new' and rapidmail sends ONE confirmation e-mail to that address; they only receive newsletters after confirming. Set double_opt_in=false only if you hold the person's documented consent: the recipient is then stored as 'active' and no e-mail is sent (refused if the address was unsubscribed before). If a deleted recipient with the same address exists it is re-activated; an existing address returns a conflict error. Never use for bulk imports. POST /recipients.

Input parameters:

- `birthdate` (string): Birth date, yyyy-mm-dd.
- `double_opt_in` (boolean): true (default): status 'new' and a confirmation e-mail is sent to the address. false: status 'active', no e-mail (only with documented consent).
- `email` (string, required): E-mail address of the recipient.
- `extra1` (string): Custom field 1 (max 255 characters).
- `extra10` (string): Custom field 10 (max 255 characters).
- `extra2` (string): Custom field 2 (max 255 characters).
- `extra3` (string): Custom field 3 (max 255 characters).
- `extra4` (string): Custom field 4 (max 255 characters).
- `extra5` (string): Custom field 5 (max 255 characters).
- `extra6` (string): Custom field 6 (max 255 characters).
- `extra7` (string): Custom field 7 (max 255 characters).
- `extra8` (string): Custom field 8 (max 255 characters).
- `extra9` (string): Custom field 9 (max 255 characters).
- `firstname` (string): First name.
- `foreign_id` (string): Your own external id for this contact.
- `gender` (string): Gender.
- `lastname` (string): Last name.
- `mailtype` (string): Preferred mail format.
- `recipientlist_id` (integer, required): rapidmail recipient list id to add the recipient to.
- `test_mode` (boolean): true: validate only, nothing is saved and no e-mail is sent.
- `title` (string): Academic title, e.g. Prof. Dr.
- `zip` (string): Postal code (max 7 characters).

### `rapidmail_update_recipient` (~362 tokens)

Update recipient

WRITE: partially update ONE recipient (only the fields you pass change): e-mail, name, custom fields. The status and the recipient list cannot be changed here, and no e-mail is sent. An e-mail address that already exists in the list returns a conflict error. PATCH /recipients/{id}.

Input parameters:

- `birthdate` (string): Birth date, yyyy-mm-dd.
- `email` (string): New e-mail address.
- `extra1` (string): Custom field 1 (max 255 characters).
- `extra10` (string): Custom field 10 (max 255 characters).
- `extra2` (string): Custom field 2 (max 255 characters).
- `extra3` (string): Custom field 3 (max 255 characters).
- `extra4` (string): Custom field 4 (max 255 characters).
- `extra5` (string): Custom field 5 (max 255 characters).
- `extra6` (string): Custom field 6 (max 255 characters).
- `extra7` (string): Custom field 7 (max 255 characters).
- `extra8` (string): Custom field 8 (max 255 characters).
- `extra9` (string): Custom field 9 (max 255 characters).
- `firstname` (string): First name.
- `foreign_id` (string): Your own external id for this contact.
- `gender` (string): Gender.
- `lastname` (string): Last name.
- `mailtype` (string): Preferred mail format.
- `recipient_id` (integer, required): rapidmail recipient id.
- `title` (string): Academic title, e.g. Prof. Dr.
- `zip` (string): Postal code (max 7 characters).

### `rapidmail_unsubscribe_recipient` (~82 tokens)

Unsubscribe recipient

WRITE: remove ONE recipient from their list. rapidmail only soft-deletes the record (status 'deleted', as if the person had unsubscribed) and the statistics count it as an unsubscription. No goodbye e-mail is sent. Single recipient only. DELETE /recipients/{id}.

Input parameters:

- `recipient_id` (integer, required): rapidmail recipient id.

### `rapidmail_list_mailings` (~219 tokens)

List mailings

List newsletters (mailings) with status, subject, sender, send time, recipient count and recipient lists. Filter by status, recipient list, created / updated / sent date. Read only: mailings are never created, sent or scheduled by this server. GET /mailings.

Input parameters:

- `created_since` (string): Only mailings created since this date/time.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `recipientlist_id` (integer): Only mailings sent to this recipient list.
- `sent_from` (string): Only mailings sent from this date/time.
- `sent_to` (string): Only mailings sent up to this date/time (after sent_from).
- `sort_by` (string): Sort field.
- `sort_order` (string): Sort direction.
- `status` (string): Mailing status, e.g. draft, scheduled, sending, sent.
- `updated_since` (string): Only mailings updated since this date/time.

### `rapidmail_get_mailing` (~53 tokens)

Get mailing

One mailing by id: status, subject, sender, destinations (recipient lists), send time, size and attachments. GET /mailings/{id}.

Input parameters:

- `mailing_id` (integer, required): rapidmail mailing id.

### `rapidmail_get_mailing_stats` (~52 tokens)

Get mailing statistics

Statistics of one sent mailing (opens, clicks, bounces, unsubscriptions and similar totals). GET /mailings/{id}/stats.

Input parameters:

- `mailing_id` (integer, required): rapidmail mailing id.

### `rapidmail_list_mailing_activity` (~97 tokens)

List mailing recipient activity

The recipients a mailing went to and what each did (delivered, opened, clicked, bounced). Detailed event information is only available if the respective plugin is enabled in the rapidmail account. GET /mailings/{id}/stats/activity.

Input parameters:

- `mailing_id` (integer, required): rapidmail mailing id.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `rapidmail_get_mailing_recipient_activity` (~73 tokens)

Get one recipient's activity in a mailing

Delivery and engagement details of one recipient of one mailing. GET /mailings/{id}/stats/activity/{mailingrecipient_id}.

Input parameters:

- `mailing_id` (integer, required): rapidmail mailing id.
- `mailingrecipient_id` (integer, required): The mailing-recipient id from rapidmail_list_mailing_activity.

### `rapidmail_list_mailing_folders` (~33 tokens)

List mailing folders

The folders used to organise mailings, with id and name. GET /mailings/folders.

### `rapidmail_list_blacklist` (~130 tokens)

List blacklist entries

The account's blacklist: e-mail addresses, domains and patterns that never receive mailings, with their type, source and dates. GET /blacklist.

Input parameters:

- `created_since` (string): Only entries created since this date/time.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Entries per page, 1-1000 (default 25).
- `pattern` (string): Only entries matching this pattern.
- `updated_since` (string): Only entries updated since this date/time.

### `rapidmail_list_transactional_emails` (~210 tokens)

List transactional e-mails

Transactional (SMTP) e-mails sent through the rapidmail account: sender, recipient, subject, status (queued, delivered, bounced...), delivery diagnostics and open/click counts. Metadata only, no message bodies. Filter by date, status, project or address. GET /trx/emails.

Input parameters:

- `date_from` (string): From date, yyyy-mm-dd (not older than the account's retention).
- `date_to` (string): To date, yyyy-mm-dd.
- `from` (string): Sender name or address.
- `has_attachments` (boolean): Only mails with (true) or without (false) attachments.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `project_id` (array): Only these transactional-mail project ids.
- `status` (array): Only these delivery statuses.
- `subject` (string): Subject text.
- `to` (string): Recipient name or address.

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the rapidmail MCP by usefulapi server?

rapidmail MCP by usefulapi is listed in the public MCP registry as io.usefulapi/rapidmail. Read rapidmail lists, recipients, mailings and stats; add, update or unsubscribe one recipient. This page covers its hosted endpoint (https://rapidmail.usefulapi.io/mcp).

### Is the rapidmail MCP by usefulapi server safe to use?

rapidmail MCP by usefulapi scores 64 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 rapidmail MCP by usefulapi server expose?

rapidmail MCP by usefulapi exposes 16 tools: rapidmail_list_recipientlists, rapidmail_get_recipientlist, rapidmail_get_recipientlist_activity_stats, rapidmail_list_recipients, rapidmail_get_recipient, and 11 more. Their descriptions and schemas cost roughly 2,305 tokens of context every time the server is loaded.

### Does the rapidmail MCP by usefulapi server require authentication?

Yes. rapidmail MCP by usefulapi 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 rapidmail MCP by usefulapi server still maintained?

rapidmail MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

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