com.mcparmory/mailtrap vs Parse-DMARC MCP Server
com.mcparmory/mailtrap is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Parse-DMARC MCP Server is an MCP server published by meysam81. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.mcparmory/mailtrap |  Parse-DMARC MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Downloads/month (PyPI): 812 Downloads/week (PyPI): 155 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Listed Version: 1.4.7 Forks (GitHub): 26 Stars (GitHub): 224 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.0.2 Downloads/month (PyPI): 812 Downloads/week (PyPI): 155 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | com.mcparmory/mailtrap | Parse-DMARC MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 32 (worse) | 224 (better) |
| Forks (GitHub) (differs) | 4 (worse) | 26 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcparmory-mailtrap) | On your machine (ghcr.io/meysam81/parse-dmarc:v1.4.7) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mcparmory/registry | github.com/meysam81/parse-dmarc |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.mcparmory/mailtrap
Send emails and manage sending domains, suppression lists, and delivery analytics
Parse-DMARC MCP Server
Lightweight DMARC parser: auto-fetch email reports, visualize compliance in a single all-in-one app
How to run each
com.mcparmory/mailtrap As a local MCP server: PyPI package
claude mcp add --transport stdio mailtrap -- uvx mcparmory-mailtrapParse-DMARC MCP Server As a local MCP server: Docker image
claude mcp add --transport stdio parse-dmarc -- docker run -i --rm ghcr.io/meysam81/parse-dmarc:v1.4.7Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: com.mcparmory/mailtrap · What it can do: Parse-DMARC MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.