Mailtrap
NPM · MCP-MAILTRAP · SCANNED SEP 29
Official MCP Server for Mailtrap
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 114 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 10495 tokens (~83/item across 125 items; 125 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
- All 25 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 125 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
How do I install the Mailtrap MCP server?
Mailtrap runs locally as an npm package, launched with npx -y mcp-mailtrap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-mailtrap
claude mcp add io-mailtrap-mcp -- npx -y mcp-mailtrap
{
"mcpServers": {
"io-mailtrap-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-mailtrap"
]
}
}
} {
"servers": {
"io-mailtrap-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-mailtrap"
]
}
}
} codex mcp add io-mailtrap-mcp -- npx -y mcp-mailtrap
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-mailtrap-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-mailtrap"
],
"enabled": true
}
}
} openclaw mcp add io-mailtrap-mcp --command npx --arg -y --arg mcp-mailtrap
mcp_servers:
io-mailtrap-mcp:
command: "npx"
args: ["-y", "mcp-mailtrap"] {
"McpServers": {
"io-mailtrap-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-mailtrap"
]
}
}
} assistant mcp add io-mailtrap-mcp -t stdio -c npx -a -y mcp-mailtrap
{
"mcpServers": {
"io-mailtrap-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-mailtrap"
]
}
}
} 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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 29 Sept 2026 · Analysed npm/mcp-mailtrap@0.9.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Deprecated | 1 |
| Stale | 35 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
reply-to-inbound-message ~224
Reply to an inbound message (sends to the original sender). Sends a real email.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | – | File attachments. |
| bcc | array | – | Optional BCC recipients as `{ email, name? }` objects (bare email strings also accepted) |
| category | string | – | Message category. |
| cc | array | – | Optional CC recipients as `{ email, name? }` objects (bare email strings also accepted) |
| custom_variables | object | – | Custom variables. |
| from | object | – | Sender. Rejected for Mailtrap-hosted inboxes; required for custom-domain inboxes. |
| headers | object | – | Custom headers. |
| html | string | – | HTML body. |
| inbox_id | number | yes | The inbox ID. |
| message_id | string | yes | The message ID to reply to. |
| reply_to | object | – | Reply-To address. |
| text | string | – | Plain-text body. |
| to | array | – | Recipients. Defaults to the original sender for reply/reply_all when omitted; required for forward. |
No output schema declared.
No examples provided.
reset-api-token ~144
Reset (rotate) an API token by ID. The response includes the **new** secret `token` value — returned only on this call, so store it immediately. The previous token is invalidated.
| Name | Type | Req | Description |
|---|---|---|---|
| api_token_id | number | yes | ID of the API token. |
| expires_at | string|null | – | Optional expiration for the new token as an ISO 8601 date-time (e.g. 2027-06-01T00:00:00Z). Omit for the server default (1 year). Pass an explicit null for a token that never expires. Past values or… |
No output schema declared.
No examples provided.
reset-email-campaign ~48
Reset a `scheduled` email campaign back to `draft`; only `scheduled` campaigns can be reset.
| Name | Type | Req | Description |
|---|---|---|---|
| email_campaign_id | integer | yes | Unique identifier of the email campaign to reset. |
No output schema declared.
No examples provided.
reset-sandbox-credentials ~34
Reset the SMTP credentials for a sandbox
| Name | Type | Req | Description |
|---|---|---|---|
| sandbox_id | number | yes | ID of the sandbox to act on |
No output schema declared.
No examples provided.
reset-sandbox-email-address ~37
Generate a new receive-by-email address for a sandbox
| Name | Type | Req | Description |
|---|---|---|---|
| sandbox_id | number | yes | ID of the sandbox to act on |
No output schema declared.
No examples provided.
schedule-email-campaign ~134
Schedule a `draft` email campaign to start sending at `datetime` (ISO 8601, must be in the future and no more than 1 month ahead); only `draft` campaigns can be scheduled.
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | yes | When to send the campaign (ISO 8601, e.g. `2026-09-01T09:00:00Z` or with a UTC offset). Must be in the future and no more than 1 month ahead, otherwise the request is rejected with `422`. |
| email_campaign_id | integer | yes | Unique identifier of the email campaign to schedule. |
No output schema declared.
No examples provided.
send-email ~366
Send an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | array | – | Optional BCC recipients as `{ email, name? }` objects (bare email strings also accepted) |
| category | string | – | Optional email category for tracking. Must be omitted when `template_uuid` is set. |
| cc | array | – | Optional CC recipients as `{ email, name? }` objects (bare email strings also accepted) |
| from | object | – | Sender as `{ email, name? }` (a bare email string is also accepted). Omit if `DEFAULT_FROM_EMAIL` is set. |
| html | string | – | Optional HTML version of the email body. Must be omitted when `template_uuid` is set. |
| subject | string | – | Email subject line. Required for inline (text/html) sends; must be omitted when `template_uuid` is set. |
| template_uuid | string | – | Use a Mailtrap email template instead of inline content. When set, `subject`, `text`, `html`, and `category` must be omitted (per Mailtrap API). |
| template_variables | object | – | Variables substituted into the template referenced by `template_uuid`. Only allowed together with `template_uuid`; rejected otherwise. |
| text | string | – | Email body text. Required (alongside or instead of `html`) for inline sends; must be omitted when `template_uuid` is set. |
| to | array | – | Recipients as an array of `{ email, name? }` objects (bare email strings are also accepted as items). Optional if `cc` or `bcc` is provided; at least one of `to`/`cc`/`bcc` must contain a recipient. |
No output schema declared.
No examples provided.
send-sandbox-email ~406
Send an email in sandbox mode to a test inbox without delivering to your recipients
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | array | – | Optional BCC recipients as `{ email, name? }` objects (bare email strings also accepted) |
| category | string | – | Optional email category for tracking. Must be omitted when `template_uuid` is set. |
| cc | array | – | Optional CC recipients as `{ email, name? }` objects (bare email strings also accepted) |
| from | object | – | Sender as `{ email, name? }` (a bare email string is also accepted). Omit if `DEFAULT_FROM_EMAIL` is set. |
| html | string | – | Optional HTML version of the email body. Must be omitted when `template_uuid` is set. |
| subject | string | – | Email subject line. Required for inline (text/html) sends; must be omitted when `template_uuid` is set. |
| template_uuid | string | – | Use a Mailtrap email template instead of inline content. When set, `subject`, `text`, `html`, and `category` must be omitted (per Mailtrap API). |
| template_variables | object | – | Variables substituted into the template referenced by `template_uuid`. Only allowed together with `template_uuid`; rejected otherwise. |
| test_inbox_id | number | – | Mailtrap test inbox ID. Optional if MAILTRAP_TEST_INBOX_ID env var is set. Use to target a specific inbox. |
| text | string | – | Email body text. Required (alongside or instead of `html`) for inline sends; must be omitted when `template_uuid` is set. |
| to | array | – | Recipients as an array of `{ email, name? }` objects (bare email strings as items, or a comma-separated string of plain emails, are also accepted). Optional if `cc` or `bcc` is provided; at least one… |
No output schema declared.
No examples provided.
send-sending-domain-setup-instructions ~54
Email DNS setup instructions for a sending domain to a given address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to send DNS setup instructions to | |
| sending_domain_id | number | yes | Sending domain ID |
No output schema declared.
No examples provided.
show-sandbox-email-message ~155
Show sandbox email message details and content from the sandbox test inbox. Optionally include spam report (SpamAssassin score) and HTML analysis (client compatibility) for email testing workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| include_html_analysis | boolean | – | When true, include HTML analysis (client compatibility, problematic elements). Critical for email client testing. |
| include_spam_report | boolean | – | When true, include spam report (SpamAssassin score and details). Critical for deliverability testing. |
| message_id | number | yes | ID of the sandbox email message to retrieve |
| test_inbox_id | number | – | Mailtrap test inbox ID. Optional if MAILTRAP_TEST_INBOX_ID env var is set. Use to target a specific inbox. |
No output schema declared.
No examples provided.
start-email-campaign ~46
Start sending a `draft` email campaign immediately; only `draft` campaigns can be started.
| Name | Type | Req | Description |
|---|---|---|---|
| email_campaign_id | integer | yes | Unique identifier of the email campaign to start. |
No output schema declared.
No examples provided.
terminate-email-campaign ~54
Terminate an email campaign that is currently sending (`started`, `queued`, or `paused`), aborting the in-flight send.
| Name | Type | Req | Description |
|---|---|---|---|
| email_campaign_id | integer | yes | Unique identifier of the email campaign to terminate. |
No output schema declared.
No examples provided.
update-company-info ~147
Update the company info of a sending domain.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address. |
| city | string | – | City. |
| country | string | – | Country. |
| info_level | string | – | Whether the sender is a business or an individual. |
| name | string | – | Company or individual name. |
| phone | string | – | Phone number. |
| privacy_policy_url | string | – | URL of the privacy policy page. |
| sending_domain_id | integer | yes | Sending domain ID |
| terms_of_service_url | string | – | URL of the terms of service page. |
| website_url | string | – | Company website URL. |
| zip_code | string | – | ZIP or postal code. |
No output schema declared.
No examples provided.
update-contact ~186
Update a contact (identified by ID or email). `list_ids` replaces the membership set; `list_ids_included`/`list_ids_excluded` add/remove without disturbing the rest.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_identifier | string | yes | Contact ID or email to update. |
| string | – | New email address for the contact. | |
| fields | object | – | Custom field values to set, keyed by merge tag. String, number, or boolean values. |
| list_ids | array | – | Replace the contact's list memberships with this exact set of list IDs. |
| list_ids_excluded | array | – | List IDs to remove the contact from. |
| list_ids_included | array | – | List IDs to add the contact to (additive). |
| unsubscribed | boolean | – | Move the contact to `unsubscribed` (`true`) or `subscribed` (`false`) status. |
No output schema declared.
No examples provided.
update-contact-field ~94
Update a contact field definition. Any combination of `name`, `merge_tag`, or `data_type` can be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| data_type | string | – | New data type for the field. |
| field_id | number | yes | ID of the contact field to update. |
| merge_tag | string | – | New merge tag for the field. Must be unique. |
| name | string | – | New display name for the field. |
No output schema declared.
No examples provided.
update-contact-list ~43
Rename an existing contact list.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | ID of the contact list to update. |
| name | string | yes | New name for the contact list. |
No output schema declared.
No examples provided.
update-email-campaign ~285
Update a `draft` email campaign; only the provided fields change, and campaigns in any other state cannot be updated.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_list_ids | array | – | IDs of contact lists to send to. Treated as the full set of included lists — lists not listed are removed. |
| contact_segment_ids | array | – | IDs of contact segments to send to. Treated as the full set of included segments. |
| delivery_mode | string | – | How the campaign is delivered. `rapid` sends as fast as possible; `gradual` throttles sending to `delivery_options.emails_per_hour`. |
| delivery_options | object | – | Delivery throttling options. Applies when `delivery_mode` is `gradual`. |
| domain_id | integer | – | ID of the verified sending domain used for the campaign, as returned by the Sending Domains endpoints. |
| email_campaign_id | integer | yes | Unique identifier of the email campaign to update. |
| from_display_name | string | – | Display name shown in the From header. |
| from_local_part | string | – | Local part (before the @) of the From address. |
| name | string | – | Campaign name. |
| reply_to | object | – | Reply-To address parts. |
| template_attributes | object | – | Inline email template — the campaign's template is edited in place. Updates are partial: only the sub-fields you provide change. |
No output schema declared.
No examples provided.
update-inbound-folder ~38
Rename an inbound folder.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The inbound folder ID. |
| name | string | yes | The new folder name. |
No output schema declared.
No examples provided.
update-inbound-inbox ~50
Rename an inbound inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The inbound folder ID. |
| inbox_id | number | yes | The inbox ID. |
| name | string | yes | The new inbox name. |
No output schema declared.
No examples provided.
update-sandbox-inbox ~61
Update a sandbox inbox name or email username
| Name | Type | Req | Description |
|---|---|---|---|
| email_username | string | – | New email username for the inbox |
| inbox_id | number | yes | ID of the sandbox inbox to update |
| name | string | – | New name for the inbox |
No output schema declared.
No examples provided.
update-sandbox-message ~79
Mark a sandbox message as read or unread
| Name | Type | Req | Description |
|---|---|---|---|
| is_read | boolean | yes | Mark the message as read (true) or unread (false) |
| message_id | number | yes | ID of the sandbox message to update |
| sandbox_id | number | – | Sandbox ID. Falls back to MAILTRAP_SANDBOX_ID env var if omitted. |
No output schema declared.
No examples provided.
update-sandbox-project ~47
Rename an existing sandbox project
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | New name for the project (2–100 characters) |
| project_id | number | yes | ID of the project to update |
No output schema declared.
No examples provided.
update-sending-domain ~133
Update a sending domain's tracking and inbound settings.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_unsubscribe_link_enabled | boolean | – | Automatically add an unsubscribe link to emails. |
| click_tracking_enabled | boolean | – | Track clicks on links in emails sent from this domain. |
| inbound_enabled | boolean | – | Allow the domain to be attached to an inbound inbox as a catch-all. |
| open_tracking_enabled | boolean | – | Track opens on emails sent from this domain. |
| sending_domain_id | integer | yes | Sending domain ID |
| tracking_opt_out_enabled | boolean | – | Add the tracking opt-out link to tracked emails. Requires open or click tracking. |
No output schema declared.
No examples provided.
update-template ~90
Update an existing email template
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | New category for the template |
| html | string | – | New HTML content of the template |
| name | string | – | New name for the template |
| subject | string | – | New email subject line |
| template_id | number | yes | ID of the template to update |
| text | string | – | New plain text version of the template |
No output schema declared.
No examples provided.
update-webhook ~164
Update a webhook's mutable fields (`url`, `active`, `payload_format`, `event_types`, `inbound_inbox_id`). `webhook_type`, `sending_stream`, and `domain_id` cannot be changed after creation.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Enable or disable the webhook. |
| event_types | array | – | Events to subscribe to. Applies only to `email_sending` webhooks. |
| inbound_inbox_id | number | – | ID of the inbound inbox the webhook is linked to. Applicable only for `inbound_receiving` webhooks. |
| payload_format | string | – | Payload encoding. |
| url | string | – | New URL that Mailtrap will POST webhook events to. |
| webhook_id | number | yes | ID of the webhook to update |
No output schema declared.
No examples provided.
What is the Mailtrap MCP server?
Mailtrap is an MCP server listed in the public MCP registry as io.mailtrap/mcp. Official MCP Server for Mailtrap. This page covers its npm package (mcp-mailtrap).
Is the Mailtrap MCP server safe to use?
Mailtrap scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. It declares no install or post-install scripts. 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 Mailtrap MCP server expose?
Mailtrap exposes 125 tools: send-email, batch-send-transactional-email, batch-send-bulk-email, create-template, list-templates, and 120 more. Their descriptions and schemas cost roughly 10,495 tokens of context every time the server is loaded.
Is the Mailtrap MCP server still maintained?
Mailtrap is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Mailtrap MCP server under?
Mailtrap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.