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 →
batch-send-bulk-email ~123
Send a batch of bulk emails (Mailtrap bulk-stream API) in one call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include at least one of `to`/`cc`/`bcc`.
| Name | Type | Req | Description |
|---|---|---|---|
| base | object | – | Shared fields applied to every request in the batch. Each request can override individual fields. |
| requests | array | yes | Per-recipient messages. Each request must include at least one recipient via `to`, `cc`, or `bcc`; other fields override `base`. |
No output schema declared.
No examples provided.
batch-send-sandbox-email ~160
Send a batch of emails in sandbox mode to a test inbox in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Requires `sandbox_id` or the MAILTRAP_SANDBOX_ID env var.
| Name | Type | Req | Description |
|---|---|---|---|
| base | object | – | Shared fields applied to every request in the batch. Each request can override individual fields. |
| requests | array | yes | Per-recipient messages. Each request must include at least one recipient via `to`, `cc`, or `bcc`; other fields override `base`. |
| sandbox_id | number | – | Mailtrap sandbox (test inbox) ID. Optional if MAILTRAP_SANDBOX_ID env var is set. Use to target a specific sandbox. |
No output schema declared.
No examples provided.
batch-send-transactional-email ~108
Send a batch of transactional emails in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include `to`.
| Name | Type | Req | Description |
|---|---|---|---|
| base | object | – | Shared fields applied to every request in the batch. Each request can override individual fields. |
| requests | array | yes | Per-recipient messages. Each request must include at least one recipient via `to`, `cc`, or `bcc`; other fields override `base`. |
No output schema declared.
No examples provided.
bulk-update-permissions ~119
Bulk create, update, or destroy permissions for an account access. Existing (resource_type, resource_id) pairs are updated; new ones are created. Set `destroy: true` to remove.
| Name | Type | Req | Description |
|---|---|---|---|
| account_access_id | number | yes | ID of the account access whose permissions are being updated. |
| permissions | array | yes | Permission entries to create, update, or destroy. Combinations of `resource_type` + `resource_id` that already exist are updated; new combinations are created. Set `destroy: true` to remove an existi… |
No output schema declared.
No examples provided.
cancel-email-campaign ~50
Cancel a `scheduled` email campaign, returning it to `draft`; only `scheduled` campaigns can be cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| email_campaign_id | integer | yes | Unique identifier of the email campaign to cancel. |
No output schema declared.
No examples provided.
clean-sandbox-inbox ~44
Delete all messages from a sandbox inbox without deleting the inbox itself
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | number | yes | ID of the sandbox inbox to clean (delete all messages from) |
No output schema declared.
No examples provided.
create-api-token ~165
Create a new API token. The response includes the secret `token` value — this is the **only time** the full token is returned, so store it immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at | string|null | – | Optional token expiration 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 values more… |
| name | string | yes | Display name for the API token. |
| resources | array | – | Optional list of resource permissions to attach to the token. Each entry pins the token to a specific resource at a given access level. |
No output schema declared.
No examples provided.
create-company-info ~153
Set the company info of a sending domain, required for domain compliance verification.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address. |
| city | string | yes | City. |
| country | string | yes | Country. |
| info_level | string | – | Whether the sender is a business or an individual. |
| name | string | yes | 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 | yes | Company website URL. |
| zip_code | string | yes | ZIP or postal code. |
No output schema declared.
No examples provided.
create-contact ~129
Create a new contact. Requires `email`; optionally accepts custom `fields`, `list_ids` to subscribe to, and `unsubscribed` to start in unsubscribed status.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address of the contact. | |
| fields | object | – | Custom field values keyed by the field's merge tag (e.g. `first_name`). Values may be string, number, or boolean. |
| list_ids | array | – | IDs of contact lists to add this contact to. |
| unsubscribed | boolean | – | If true, the contact is created in `unsubscribed` status. |
No output schema declared.
No examples provided.
create-contact-event ~101
Record a contact event (by `name` + arbitrary `params`) against a contact ID or email. Used to trigger automations.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_identifier | string | yes | Contact ID or email to attach the event to. |
| name | string | yes | Event name. Used to match contact-list automations triggered by this event. |
| params | object | yes | Arbitrary key/value parameters for the event. Values may be string, number, boolean, or null. |
No output schema declared.
No examples provided.
create-contact-export ~60
Export contacts matching a set of AND-combined filters. Returns an export job; poll status with `get-contact-export` to retrieve the download URL.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | yes | Filters that select which contacts to include in the export. AND-combined. |
No output schema declared.
No examples provided.
create-contact-field ~88
Create a new contact field definition. `merge_tag` must be unique and is used in template variables.
| Name | Type | Req | Description |
|---|---|---|---|
| data_type | string | yes | Data type stored in this field. |
| merge_tag | string | yes | Merge tag used in template variables (e.g. `first_name`). Must be unique. |
| name | string | yes | Display name of the field (e.g. "First Name"). |
No output schema declared.
No examples provided.
create-contact-import ~65
Bulk import contacts. Returns an import job record; poll status via `get-contact-import`.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | Contacts to import. Each entry needs at least an `email`; optionally include custom `fields`, `list_ids_included`, and `list_ids_excluded`. |
No output schema declared.
No examples provided.
create-contact-list ~28
Create a new contact list.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new contact list. |
No output schema declared.
No examples provided.
create-email-campaign ~267
Create a new email campaign in the `draft` state; requires `name`, `domain_id`, `from_local_part`, and a `template_attributes.subject`.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_list_ids | array | – | IDs of contact lists to send to. Treated as the full set of included lists. Combine with `contact_segment_ids` to target both. |
| 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 | yes | ID of the verified sending domain used for the campaign, as returned by the Sending Domains endpoints. |
| from_display_name | string | – | Display name shown in the From header. |
| from_local_part | string | yes | Local part (before the @) of the From address. |
| name | string | yes | Campaign name. |
| reply_to | object | – | Reply-To address parts. |
| template_attributes | object | yes | Inline email template — the campaign's subject and design. |
No output schema declared.
No examples provided.
create-inbound-folder ~26
Create a new inbound folder.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The folder name. |
No output schema declared.
No examples provided.
create-inbound-inbox ~106
Create a new inbound inbox in a folder. Omit `domain_id` for a Mailtrap-hosted inbox; pass it for a custom-domain (catch-all) inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | number | – | Optional. Attach the inbox to a custom sending domain (catch-all inbox). Omit for a standard Mailtrap-hosted inbox. |
| folder_id | number | yes | The inbound folder ID to create the inbox in. |
| name | string | yes | The inbox name. |
No output schema declared.
No examples provided.
create-sandbox-inbox ~57
Create a new sandbox test inbox within a project. Returns SMTP credentials for the new inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the inbox |
| project_id | number | yes | ID of the project to create the inbox in |
No output schema declared.
No examples provided.
create-sandbox-project ~37
Create a new sandbox project to group test inboxes
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the project (2–100 characters) |
No output schema declared.
No examples provided.
create-sending-domain ~32
Create a new sending domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain_name | string | yes | Domain name (e.g. example.com) |
No output schema declared.
No examples provided.
create-sub-account ~48
Create a new sub-account under the organization. Requires `MAILTRAP_ORGANIZATION_ID` and sub-account management permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Display name for the new sub-account. |
No output schema declared.
No examples provided.
create-suppression ~101
Add an email address to the account's suppression list, so Mailtrap stops delivering to it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | integer | yes | ID of the sending domain the suppression applies to, as returned by the Sending Domains tools. |
| string | yes | Email address to suppress. | |
| sending_stream | string | yes | Sending stream to suppress the address for. |
| type | string | – | Reason recorded for the suppression. Defaults to `manual import` when omitted. |
No output schema declared.
No examples provided.
create-template ~80
Create a new email template
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Template category (optional, defaults to 'General') |
| html | string | – | HTML content of the template (optional) |
| name | string | yes | Name of the template |
| subject | string | yes | Email subject line |
| text | string | – | Plain text version of the template (optional) |
No output schema declared.
No examples provided.
create-tracking-opt-out ~69
Exclude an email address from open and click tracking for a sending domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | integer | yes | ID of the sending domain the opt-out applies to, as returned by the Sending Domains tools. |
| string | yes | Email address to opt out of open and click tracking. |
No output schema declared.
No examples provided.
create-webhook ~309
Create a webhook. `webhook_type` may be `email_sending`, `audit_log`, or `inbound_receiving`; for `inbound_receiving`, `inbound_inbox_id` is optional (scopes the webhook to one inbox — omit to apply to all inboxes). The response includes a `signing_secret` for verifying webhook payload signatures — this secret is returned only on creation, so store it now.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the webhook is enabled. Defaults to true. |
| domain_id | number | – | Sending domain ID to scope this webhook to. Applies only to `email_sending` webhooks. |
| 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; optional — omit to apply to all inboxes in the account. |
| payload_format | string | – | Payload encoding. Defaults to `json`. |
| sending_stream | string | – | Sending stream this webhook subscribes to. Applies only to `email_sending` webhooks. |
| url | string | yes | URL that Mailtrap will POST webhook events to. |
| webhook_type | string | yes | Webhook category. `email_sending` for delivery/open/click/etc events, `audit_log` for account audit events, `inbound_receiving` for inbound inbox events. |
No output schema declared.
No examples provided.
delete-api-token ~41
Permanently delete an API token by ID. The token can no longer authenticate after deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| api_token_id | number | yes | ID of the API token. |
No output schema declared.
No examples provided.
delete-contact ~40
Permanently delete a contact by ID or email. Returns the deleted contact record when available.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_identifier | string | yes | Contact ID or email to delete. |
No output schema declared.
No examples provided.
delete-contact-field ~34
Permanently delete a contact field definition by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| field_id | number | yes | ID of the contact field to delete. |
No output schema declared.
No examples provided.
delete-contact-list ~33
Permanently delete a contact list by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | number | yes | ID of the contact list to delete. |
No output schema declared.
No examples provided.
delete-email-campaign ~47
Delete an email campaign by ID; only a campaign in the `draft` state can be deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| email_campaign_id | integer | yes | Unique identifier of the email campaign to delete. |
No output schema declared.
No examples provided.
delete-inbound-folder ~36
Permanently delete an inbound folder along with all of its inboxes.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The inbound folder ID. |
No output schema declared.
No examples provided.
delete-inbound-inbox ~41
Permanently delete an inbound inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | number | yes | The inbound folder ID. |
| inbox_id | number | yes | The inbox ID. |
No output schema declared.
No examples provided.
delete-inbound-message ~39
Permanently delete an inbound message.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | number | yes | The inbox ID. |
| message_id | string | yes | The message ID. |
No output schema declared.
No examples provided.
delete-inbound-thread ~39
Permanently delete an inbound thread.
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | number | yes | The inbox ID. |
| thread_id | string | yes | The thread ID. |
No output schema declared.
No examples provided.
delete-sandbox-inbox ~35
Delete a sandbox inbox and all its messages
| Name | Type | Req | Description |
|---|---|---|---|
| inbox_id | number | yes | ID of the sandbox inbox to delete |
No output schema declared.
No examples provided.
delete-sandbox-message ~54
Delete a single sandbox message
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | number | yes | ID of the sandbox message |
| sandbox_id | number | – | Sandbox ID. Falls back to MAILTRAP_SANDBOX_ID env var if omitted. |
No output schema declared.
No examples provided.
delete-sandbox-project ~34
Delete a sandbox project and all its inboxes
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | number | yes | ID of the project to delete |
No output schema declared.
No examples provided.
delete-sending-domain ~29
Delete a sending domain
| Name | Type | Req | Description |
|---|---|---|---|
| sending_domain_id | number | yes | Sending domain ID to delete |
No output schema declared.
No examples provided.
delete-suppression ~44
Delete a suppression by ID. Mailtrap will resume delivery to this email unless it gets suppressed again.
| Name | Type | Req | Description |
|---|---|---|---|
| suppression_id | string | yes | ID of the suppression to delete |
No output schema declared.
No examples provided.
delete-template ~28
Delete an existing email template
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | number | yes | ID of the template to delete |
No output schema declared.
No examples provided.
delete-tracking-opt-out ~50
Remove an email address from the tracking opt-out list, so open and click tracking applies to it again.
| Name | Type | Req | Description |
|---|---|---|---|
| tracking_opt_out_id | string | yes | ID of the tracking opt-out to delete |
No output schema declared.
No examples provided.
delete-webhook ~37
Permanently delete a webhook by ID. Returns the deleted webhook record.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | number | yes | ID of the webhook to delete |
No output schema declared.
No examples provided.
enable-sandbox-email-address ~36
Enable the 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.
forward-inbound-message ~226
Forward an inbound message to new recipients (at least one `to` is required). 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 forward. |
| reply_to | object | – | Reply-To address. |
| text | string | – | Plain-text body. |
| to | array | yes | Recipients. Defaults to the original sender for reply/reply_all when omitted; required for forward. |
No output schema declared.
No examples provided.
forward-sandbox-message ~80
Forward a sandbox message to an email address (counts against your monthly forwarding quota)
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to forward the message to | |
| message_id | number | yes | ID of the sandbox message to forward |
| sandbox_id | number | – | Sandbox ID. Falls back to MAILTRAP_SANDBOX_ID env var if omitted. |
No output schema declared.
No examples provided.
get-api-token ~52
Get an API token by ID. The secret token value is NOT returned here — only the metadata (name, last 4 digits, resources).
| Name | Type | Req | Description |
|---|---|---|---|
| api_token_id | number | yes | ID of the API token. |
No output schema declared.
No examples provided.
get-billing-usage ~32
Get the current billing cycle usage for the account (sending and testing plans, limits, and current counts).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-company-info ~36
Get the company info of a sending domain, used for domain compliance verification.
| Name | Type | Req | Description |
|---|---|---|---|
| sending_domain_id | integer | yes | Sending domain ID |
No output schema declared.
No examples provided.
get-contact ~45
Get a contact by ID or email address. Returns the full contact record including list memberships, status, and custom fields.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_identifier | string | yes | Contact ID or email address. |
No output schema declared.
No examples provided.
get-contact-export ~52
Get the status of a contact export job. Once `status` is `finished`, the `url` field holds the download link.
| Name | Type | Req | Description |
|---|---|---|---|
| export_id | number | yes | ID of the contact export job to fetch. |
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.