rapidmail MCP by usefulapi
REMOTE · RAPIDMAIL.USEFULAPI.IO
Read rapidmail lists, recipients, mailings and stats; add, update or unsubscribe one recipient.
Available components
Last scanned (1 hour ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 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 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 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
- 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 & 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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
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.
- 16 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
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 17 Oct 2026 · Probed https://rapidmail.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 rapidmail.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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://rapidmail.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://rapidmail.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://rapidmail.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://rapidmail.usefulapi.io/mcp |
| Authorisation server | https://rapidmail.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rapidmail.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/rapidmail/ |
| http (plaintext) | http://rapidmail.usefulapi.io/mcp | Inconclusive | 302 | http://rapidmail.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 →
rapidmail_create_recipient Add recipient ~496
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| string | yes | 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 | yes | 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). |
No output schema declared.
No examples provided.
rapidmail_get_mailing Get mailing ~53
One mailing by id: status, subject, sender, destinations (recipient lists), send time, size and attachments. GET /mailings/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| mailing_id | integer | yes | rapidmail mailing id. |
No output schema declared.
No examples provided.
rapidmail_get_mailing_recipient_activity Get one recipient's activity in a mailing ~73
Delivery and engagement details of one recipient of one mailing. GET /mailings/{id}/stats/activity/{mailingrecipient_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| mailing_id | integer | yes | rapidmail mailing id. |
| mailingrecipient_id | integer | yes | The mailing-recipient id from rapidmail_list_mailing_activity. |
No output schema declared.
No examples provided.
rapidmail_get_mailing_stats Get mailing statistics ~52
Statistics of one sent mailing (opens, clicks, bounces, unsubscriptions and similar totals). GET /mailings/{id}/stats.
| Name | Type | Req | Description |
|---|---|---|---|
| mailing_id | integer | yes | rapidmail mailing id. |
No output schema declared.
No examples provided.
rapidmail_get_recipient Get recipient ~47
One recipient by id: e-mail, name, status, custom fields and timestamps. GET /recipients/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | integer | yes | rapidmail recipient id. |
No output schema declared.
No examples provided.
rapidmail_get_recipientlist Get recipient list ~39
One recipient list by id. GET /recipientlists/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| recipientlist_id | integer | yes | rapidmail recipient list id. |
No output schema declared.
No examples provided.
rapidmail_get_recipientlist_activity_stats Get recipient list activity stats ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start date, yyyy-mm-dd. |
| recipientlist_id | integer | yes | rapidmail recipient list id. |
| to | string | yes | End date, yyyy-mm-dd; later than from. |
No output schema declared.
No examples provided.
rapidmail_list_blacklist List blacklist entries ~130
The account's blacklist: e-mail addresses, domains and patterns that never receive mailings, with their type, source and dates. GET /blacklist.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
rapidmail_list_mailing_activity List mailing recipient activity ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mailing_id | integer | yes | rapidmail mailing id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
rapidmail_list_mailing_folders List mailing folders ~33
The folders used to organise mailings, with id and name. GET /mailings/folders.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rapidmail_list_mailings List mailings ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
rapidmail_list_recipientlists List recipient lists ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
rapidmail_list_recipients List recipients ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
rapidmail_list_transactional_emails List transactional e-mails ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
rapidmail_unsubscribe_recipient Unsubscribe recipient ~82
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | integer | yes | rapidmail recipient id. |
No output schema declared.
No examples provided.
rapidmail_update_recipient Update recipient ~362
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| birthdate | string | – | Birth date, yyyy-mm-dd. |
| 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 | yes | rapidmail recipient id. |
| title | string | – | Academic title, e.g. Prof. Dr. |
| zip | string | – | Postal code (max 7 characters). |
No output schema declared.
No examples provided.
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.
remote · rapidmail.usefulapi.io
claude mcp add --transport http io-usefulapi-rapidmail 'https://rapidmail.usefulapi.io/mcp'
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.