MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

rapidmail MCP by usefulapi

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

Checks passed
14 / 22

0 failed · 8 not measured

Median response
108 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
16

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 108 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name rapidmail-mcp.

  • Pass
    Lists tools

    tools/list returned 16 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 108 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 108 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    86 of 86 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:34:01.61644Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using rapidmail MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http rapidmail-mcp-by-usefulapi https://rapidmail.usefulapi.io/mcp

Capabilities

Tools 16

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

Discovered
rapidmail_get_mailing

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

Discovered
rapidmail_get_mailing_recipient_activity

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

Discovered
rapidmail_get_mailing_stats

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

Discovered
rapidmail_get_recipient

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

Discovered
rapidmail_get_recipientlist

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

Discovered
rapidmail_get_recipientlist_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.

Discovered
rapidmail_list_blacklist

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

Discovered
rapidmail_list_mailing_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.

Discovered
rapidmail_list_mailing_folders

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

Discovered
rapidmail_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.

Discovered
rapidmail_list_recipientlists

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.

Discovered
rapidmail_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.

Discovered
rapidmail_list_transactional_emails

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.

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

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

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected108 ms16