Mailrith Email Marketing
REMOTE · API.MAILRITH.COM · 2 COMPONENTS
Manage Subscribers, Broadcasts, Sequences, Automations, and reporting in Mailrith.
Available components
Last scanned (11 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 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 Security91
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5943 tokens (~104/item across 57 items; 55 tools + 2 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 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety96
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 6 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "broadcasts_get_send_progress" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 0
- Tool “broadcasts_send_test” rewrote its description, which is the text the model reads security
- Tool “sequences_preflight” rewrote its description, which is the text the model reads security
- Server version: 1.1.1 → 2.0.1 functional
- 28 Sept 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
- 25 Sept 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
- 20 Sept 26 0
- DNSSEC: fail → pass ▲ security
- 5 Sept 26 0
- Server version: 1.1.0 → 1.1.1 functional
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 0
- Stability: pass → 0.97 functional
- 29 Aug 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Probed https://api.mailrith.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mailrith.com | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | da4b1af87cc48e7f0ef66a7755ddb4b7 |
| SANs: mailrith.com, *.mailrith.com | ||||||
| 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 secure
Validation of api.mailrith.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| mailrith.com. | DS published | 2371 | 13 | Verified |
| api.mailrith.com. | Verified address RRset verified with the apex keys |
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="mailrith", error="invalid_token", error_description="Authentication is required before calling Mailrith tools.", resource_metadata="https://api.mailrith.com/.well-known/oauth-protected-resource/mcp", scope="analytics:read live_actions:write subscribers:read subscribers:write subscribers:import subscribers:export segments:read segments:write tags:read tags:write forms:read forms:write form_submissions:read landing_pages:read landing_pages:write landing_page_submissions:read broadcasts:read broadcasts:write sequences:read sequences:write magic_links:read magic_links:write automations:read automations:write workspace:read email_templates:read email_templates:write custom_fields:read custom_fields:write webhooks:read webhooks:write"
Bearer realm="mailrith", error="invalid_token", error_description="Authentication is required before calling Mailrith tools.", resource_metadata="https://api.mailrith.com/.well-known/oauth-protected-resource/mcp", scope="analytics:read live_actions:write subscribers:read subscribers:write subscribers:import subscribers:export segments:read segments:write tags:read tags:write forms:read forms:write form_submissions:read landing_pages:read landing_pages:write landing_page_submissions:read broadcasts:read broadcasts:write sequences:read sequences:write magic_links:read magic_links:write automations:read automations:write workspace:read email_templates:read email_templates:write custom_fields:read custom_fields:write webhooks:read webhooks:write"Protected resource metadata
| Document | https://api.mailrith.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.mailrith.com/mcp |
| Authorisation server | https://api.mailrith.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mailrith.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.mailrith.com/mcp | HTTPS enforced | 301 | https://api.mailrith.com/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 →
subscribers_upsert Create or upsert a subscriber ~133
Creates a new subscriber when the email does not exist in the workspace. If the email already exists, the API updates the existing subscriber unless create_only is true. Effect: external-email. Retry with the same idempotency_key. Permissions: live_actions:write, subscribers:write. API reference: https://mailrith.com/developers/api-reference.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | The exact JSON request body defined by the Mailrith public API contract. |
| idempotency_key | string | – | Optional idempotency key to retry the request safely. It must not exceed 256 UTF-8 bytes. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| operation_id | string | yes | The stable Mailrith public API operation ID. |
| request_id | string | yes | The stable correlation ID for this MCP tool invocation. |
| response | – | – | – |
No examples provided.
tags_create Create a tag ~151
Creates a new tag in the authenticated workspace. The GDPR consent tag names can be created and applied like other tags when you need to apply consent collected outside Mailrith. Tag-level double opt-in fields are no longer accepted; configure double opt-in on forms and landing pages instead. Effect: workspace-change. Retry with the same idempotency_key. Permission: tags:write. API reference: https://mailrith.com/developers/api-reference.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | The exact JSON request body defined by the Mailrith public API contract. |
| idempotency_key | string | – | Optional idempotency key to retry the request safely. It must not exceed 256 UTF-8 bytes. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| operation_id | string | yes | The stable Mailrith public API operation ID. |
| request_id | string | yes | The stable correlation ID for this MCP tool invocation. |
| response | object | – | – |
No examples provided.
tags_get Get a tag ~48
Returns one Tag from the authenticated workspace. Permission: tags:read. API reference: https://mailrith.com/developers/api-reference.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id | string | yes | The Tag identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| operation_id | string | yes | The stable Mailrith public API operation ID. |
| request_id | string | yes | The stable correlation ID for this MCP tool invocation. |
| response | object | – | – |
No examples provided.
tags_list List tags ~103
Returns tags in the authenticated workspace. Permission: tags:read. Pagination: use bounded pages and returned cursors. API reference: https://mailrith.com/developers/api-reference.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of tags to return. |
| search | string | – | Filter Tags by name or description. Retrieve a known Tag ID through the item endpoint. |
| starting_after | string | – | Use the opaque cursor from the previous page to request the next page. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| operation_id | string | yes | The stable Mailrith public API operation ID. |
| request_id | string | yes | The stable correlation ID for this MCP tool invocation. |
| response | object | – | – |
No examples provided.
workspace_get Get the current workspace ~52
Returns the authenticated workspace profile and mailing context used by broadcasts, sequences, automations, forms, and magic links. Permission: workspace:read. API reference: https://mailrith.com/developers/api-reference.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | – |
| operation_id | string | yes | The stable Mailrith public API operation ID. |
| request_id | string | yes | The stable correlation ID for this MCP tool invocation. |
| response | object | – | – |
No examples provided.
How do I install the Mailrith Email Marketing MCP server?
Mailrith Email Marketing is a hosted endpoint at https://api.mailrith.com/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 · api.mailrith.com
claude mcp add --transport http com-mailrith-mailrith 'https://api.mailrith.com/mcp'
What is the Mailrith Email Marketing MCP server?
Mailrith Email Marketing is an MCP server listed in the public MCP registry as com.mailrith/mailrith. Manage Subscribers, Broadcasts, Sequences, Automations, and reporting in Mailrith. This page covers its hosted endpoint (https://api.mailrith.com/mcp).
Is the Mailrith Email Marketing MCP server safe to use?
Mailrith Email Marketing scores 93 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 Mailrith Email Marketing MCP server expose?
Mailrith Email Marketing exposes 55 tools: discovery_get_capabilities, workspace_get, sender_identities_list, sender_identities_get, analytics_create_report, and 50 more. Their descriptions and schemas cost roughly 5,776 tokens of context every time the server is loaded.
Does the Mailrith Email Marketing MCP server require authentication?
Yes. Mailrith Email Marketing 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 Mailrith Email Marketing MCP server still maintained?
Mailrith Email Marketing is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Mailrith Email Marketing MCP server?
VerifyMCP ran 13 checks on Mailrith Email Marketing, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.