Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/mailtrap

PYPI · MCPARMORY-MAILTRAP · 2 COMPONENTS

Send emails and manage sending domains, suppression lists, and delivery analytics

−15 this week 68 Trust /100

Last scanned (23 hours ago)

Scores higher than 64% of PyPI servers

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 2 of 40 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2424 tokens (~173/item across 14 items; 14 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 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
Tool Safety92
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_sending_domain_setup_instructions" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 30 Oct 26 0
    • Stability: pass → 0.97 functional
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
  • 23 Oct 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
Diagnostics

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 4 Nov 2026 · Analysed pypi/mcparmory-mailtrap@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 40 packages
Packages resolved 40
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~2,424 tokens

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 →

Tool Tokens
create_sending_domain ~106

Create a sending domain for email authentication. After creation, you'll need to add DNS records (SPF, DKIM, DMARC) and verify them before sending emails through this domain.

NameTypeReqDescription
account_idintegeryesThe unique identifier for your account. This is a positive integer that specifies which account owns the sending domain.
domain_namestringyesThe domain name you want to use for sending emails (e.g., example.com). Must be a valid hostname format.

No output schema declared.

No examples provided.

delete_sending_domain ~101

Permanently remove a sending domain from your account. This action cannot be undone and will prevent further email transmission through this domain.

NameTypeReqDescription
account_idintegeryesThe unique identifier for your account. This is a positive integer that specifies which account owns the sending domain being deleted.
sending_domain_idintegeryesThe unique identifier for the sending domain to be deleted. This is a positive integer that identifies the specific domain configuration to remove from your account.

No output schema declared.

No examples provided.

delete_suppression ~85

Remove an email address from the suppression list, allowing it to receive messages again. This operation permanently deletes the suppression record for the specified account.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account containing the suppression record. Must be a positive integer.
suppression_idintegeryesThe unique identifier for the suppression record to delete. Must be a positive integer.

No output schema declared.

No examples provided.

get_account_sending_stats ~301

Retrieve sending statistics for an account over a specified date range, with optional filtering by sending domains, streams, categories, and email service providers.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account whose sending statistics should be retrieved.
categoriesarray–Optional list of email categories to filter results (e.g., Welcome Email, Password Reset). When provided, only statistics for the specified categories are included; omit to retrieve results for all c…
email_service_providersarray–Optional list of email service providers to filter results (e.g., Google, Yahoo). When provided, only statistics for the specified ESPs are included; omit to retrieve results for all email service pr…
end_datestringyesThe end of the date range for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).
sending_domain_idsarray–Optional list of sending domain IDs to filter results. When provided, only statistics for the specified domains are included; omit to retrieve results for all sending domains.
sending_streamsarray–Optional list of sending stream types to filter results (e.g., transactional, bulk). When provided, only statistics for the specified streams are included; omit to retrieve results for all sending st…
start_datestringyesThe beginning of the date range for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).

No output schema declared.

No examples provided.

get_account_sending_stats_by_date ~271

Retrieve sending statistics for an account over a specified date range, with optional filtering by sending domains, streams, categories, and email service providers.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account whose sending statistics should be retrieved.
categoriesarray–Optional list of email categories (e.g., Welcome Email, Password Reset) to filter results. When omitted, statistics for all categories are included.
email_service_providersarray–Optional list of email service provider names (e.g., Google, Yahoo) to filter results. When omitted, statistics for all ESPs are included.
end_datestringyesThe end of the date range (inclusive) for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).
sending_domain_idsarray–Optional list of sending domain IDs to filter results. When omitted, statistics for all sending domains are included.
sending_streamsarray–Optional list of sending stream types (e.g., transactional, bulk) to filter results. When omitted, statistics for all sending streams are included.
start_datestringyesThe beginning of the date range (inclusive) for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).

No output schema declared.

No examples provided.

get_account_sending_stats_by_domains ~306

Retrieve sending statistics for an account aggregated by sending domains over a specified date range. Use optional filters to narrow results by specific domains, sending streams, message categories, or email service providers.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account whose sending statistics should be retrieved.
categoriesarray–Optional list of message categories to filter results (e.g., Welcome Email, Password Reset). When provided, only statistics for the specified categories are included; omit to include all categories.
email_service_providersarray–Optional list of email service provider names to filter results (e.g., Google, Yahoo). When provided, only statistics for the specified providers are included; omit to include all providers.
end_datestringyesThe end of the date range (inclusive) for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).
sending_domain_idsarray–Optional list of sending domain IDs to filter results. When provided, only statistics for the specified domains are included; omit to include all domains.
sending_streamsarray–Optional list of sending stream types to filter results (e.g., transactional, bulk). When provided, only statistics for the specified streams are included; omit to include all streams.
start_datestringyesThe beginning of the date range (inclusive) for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).

No output schema declared.

No examples provided.

get_account_sending_stats_by_email_service_providers ~311

Retrieve sending statistics for an account aggregated by email service providers over a specified date range. Apply optional filters by sending domain, stream type, category, or specific ESP to narrow results.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account whose sending statistics should be retrieved.
categoriesarray–Optional list of email categories to filter results (e.g., Welcome Email, Password Reset). When provided, only statistics for the specified categories are included; omit to include all categories.
email_service_providersarray–Optional list of email service provider names to filter results (e.g., Google, Yahoo). When provided, only statistics for the specified ESPs are included; omit to include all providers.
end_datestringyesThe end of the date range (inclusive) for which to include sending statistics, specified in ISO 8601 date format (YYYY-MM-DD).
sending_domain_idsarray–Optional list of sending domain IDs to filter results. When provided, only statistics for the specified domains are included; omit to include all domains.
sending_streamsarray–Optional list of sending stream types to filter results (e.g., transactional, bulk). When provided, only statistics for the specified streams are included; omit to include all streams.
start_datestringyesThe beginning of the date range (inclusive) for which to include sending statistics, specified in ISO 8601 date format (YYYY-MM-DD).

No output schema declared.

No examples provided.

get_email_log_message ~84

Retrieve a specific email message from the account's email log by its unique message identifier. The message must belong to the specified account and an accessible sending domain.

NameTypeReqDescription
account_idintegeryesThe numeric identifier of the account that owns the email message.
sending_message_idstringyesThe unique identifier (UUID) of the email message to retrieve from the log.

No output schema declared.

No examples provided.

get_sending_domain ~65

Retrieve detailed information and verification status for a specific sending domain associated with your account.

NameTypeReqDescription
account_idintegeryesThe unique identifier for your account.
sending_domain_idintegeryesThe unique identifier for the sending domain whose details and verification status you want to retrieve.

No output schema declared.

No examples provided.

get_sending_stats_by_categories ~312

Retrieve sending statistics aggregated by email categories for a specified account and date range. Use optional filters to narrow results by sending domain, stream type, category name, or email service provider.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account whose sending statistics should be retrieved.
categoriesarray–Optional list of email category names to filter results (e.g., 'Welcome Email', 'Password Reset'). When provided, only statistics for the specified categories are included; omit to include all catego…
email_service_providersarray–Optional list of email service provider names to filter results (e.g., 'Google', 'Yahoo'). When provided, only statistics for the specified providers are included; omit to include all providers.
end_datestringyesThe end of the date range (inclusive) for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).
sending_domain_idsarray–Optional list of sending domain IDs to filter results. When provided, only statistics for the specified domains are included; omit to include all domains.
sending_streamsarray–Optional list of sending stream types to filter results (e.g., 'transactional', 'bulk'). When provided, only statistics for the specified streams are included; omit to include all streams.
start_datestringyesThe beginning of the date range (inclusive) for which to retrieve statistics, specified in ISO 8601 date format (YYYY-MM-DD).

No output schema declared.

No examples provided.

list_email_logs ~186

Retrieve a paginated list of email logs for the account, filtered by sending domains accessible to the authenticated token. Results are sorted by sent_at in descending order.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account whose email logs you want to retrieve. Must be a positive integer.
filtersobject–Filter criteria to narrow results using deep object syntax (e.g., filters[field][operator] and filters[field][value]). For array values, use bracket notation (e.g., filters[field][value][]=item1). Da…
search_afterstring–Pagination cursor for fetching the next page of results. Use the message_id UUID value from the previous response's next_page_cursor field to continue pagination.

No output schema declared.

No examples provided.

list_sending_domains ~57

Retrieve all sending domains configured for an account along with their current verification status. Use this to view domain authentication and readiness for email sending.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account. Must be a positive integer.

No output schema declared.

No examples provided.

list_suppressions ~132

Retrieve a list of suppressed email addresses for your account. Suppressed addresses will not receive any emails. Results are limited to 1000 suppressions per request and can be filtered by email address or suppression date.

NameTypeReqDescription
account_idintegeryesThe unique identifier for your account.
emailstring–Filter results to a specific email address. Must be a valid email format.
start_timestring–Filter results to show only emails suppressed after this timestamp. Use ISO 8601 date-time format (e.g., 2025-01-01T00:00:00Z).

No output schema declared.

No examples provided.

send_sending_domain_setup_instructions ~107

Send DNS configuration setup instructions to a specified email address for a sending domain. This allows domain administrators to receive the necessary steps to configure DNS records for email authentication.

NameTypeReqDescription
account_idintegeryesThe unique identifier for the account that owns the sending domain.
emailstringyesThe email address where the DNS setup instructions will be sent. Must be a valid email format.
sending_domain_idintegeryesThe unique identifier for the sending domain to configure.

No output schema declared.

No examples provided.

Install

How do I install the com.mcparmory/mailtrap MCP server?

com.mcparmory/mailtrap runs locally as a PyPI package, launched with uvx mcparmory-mailtrap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcparmory-mailtrap

# add to Claude Code
claude mcp add com-mcparmory-mailtrap -- uvx mcparmory-mailtrap
Common questions

What is the com.mcparmory/mailtrap MCP server?

com.mcparmory/mailtrap is an MCP server listed in the public MCP registry as com.mcparmory/mailtrap. Send emails and manage sending domains, suppression lists, and delivery analytics. This page covers its PyPI package (mcparmory-mailtrap).

Is the com.mcparmory/mailtrap MCP server safe to use?

com.mcparmory/mailtrap scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 com.mcparmory/mailtrap MCP server expose?

com.mcparmory/mailtrap exposes 14 tools: list_sending_domains, create_sending_domain, get_sending_domain, delete_sending_domain, send_sending_domain_setup_instructions, and 9 more. Their descriptions and schemas cost roughly 2,424 tokens of context every time the server is loaded.

Is the com.mcparmory/mailtrap MCP server still maintained?

com.mcparmory/mailtrap is still listed as active in the MCP registry. We last reached this channel on 4 November 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 com.mcparmory/mailtrap MCP server under?

com.mcparmory/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.