io.github.pierre3/maildev-mcp
NUGET · MAILDEVMCP · SCANNED SEP 20
MailDev MCP server. Manage Docker containers and inspect emails from your AI editor or MCP client.
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 184 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 612 tokens (~51/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_all_emails" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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 io.github.pierre3/maildev-mcp server?
io.github.pierre3/maildev-mcp runs locally as a NuGet package, launched with dnx MailDevMcp@1.0.1 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · MailDevMcp
claude mcp add pierre3-maildev-mcp -- dnx MailDevMcp@1.0.1 --yes
{
"mcpServers": {
"pierre3-maildev-mcp": {
"command": "dnx",
"args": [
"MailDevMcp@1.0.1",
"--yes"
]
}
}
} {
"servers": {
"pierre3-maildev-mcp": {
"command": "dnx",
"args": [
"MailDevMcp@1.0.1",
"--yes"
]
}
}
} codex mcp add pierre3-maildev-mcp -- dnx MailDevMcp@1.0.1 --yes
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pierre3-maildev-mcp": {
"type": "local",
"command": [
"dnx",
"MailDevMcp@1.0.1",
"--yes"
],
"enabled": true
}
}
} mcp_servers:
pierre3-maildev-mcp:
command: "dnx"
args: ["MailDevMcp@1.0.1", "--yes"] {
"McpServers": {
"pierre3-maildev-mcp": {
"Transport": "stdio",
"Command": "dnx",
"Arguments": [
"MailDevMcp@1.0.1",
"--yes"
]
}
}
} {
"mcpServers": {
"pierre3-maildev-mcp": {
"command": "dnx",
"args": [
"MailDevMcp@1.0.1",
"--yes"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −2
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 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.
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 20 Sept 2026 · Analysed nuget/MailDevMcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unreadable |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
delete_all_emails ~18
Delete all received emails in MailDev.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_email ~33
Delete a single email by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Email ID to delete (obtained from list_emails) |
No output schema declared.
No examples provided.
get_attachment_content ~52
Get the raw Base64-encoded content of an email attachment.
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentIndex | integer | yes | Attachment index (0-based) |
| emailId | string | yes | Email ID (obtained from list_emails) |
No output schema declared.
No examples provided.
get_email ~37
Get the details of an email by ID, including attachment information.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Email ID (obtained from list_emails) |
No output schema declared.
No examples provided.
get_email_html ~35
Get the HTML body of an email by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Email ID (obtained from list_emails) |
No output schema declared.
No examples provided.
list_emails ~19
Retrieve the list of received emails in MailDev.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
maildev_status ~17
Check the running status of MailDev.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_emails ~83
Search received emails by subject, sender, or recipient. Returns matching emails.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string|null | – | Filter by sender address (case-insensitive partial match, optional) |
| subject | string|null | – | Filter by subject (case-insensitive partial match, optional) |
| to | string|null | – | Filter by recipient address (case-insensitive partial match, optional) |
No output schema declared.
No examples provided.
start_maildev ~106
Start the MailDev Docker container.
| Name | Type | Req | Description |
|---|---|---|---|
| apiPort | integer | – | Web UI / API port number (default: 1080) |
| enableSsl | boolean | – | Enable TLS for SMTP connections (default: false) |
| smtpPassword | string|null | – | SMTP authentication password (required when smtpUser is specified) |
| smtpPort | integer | – | SMTP port number (default: 1025) |
| smtpUser | string|null | – | SMTP authentication username (omit to disable authentication) |
No output schema declared.
No examples provided.
stop_maildev ~18
Stop and remove the MailDev Docker container.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_attachment ~78
Verify that an email attachment matches the original data. Accepts Base64-encoded original data and compares it byte-by-byte with the received attachment.
| Name | Type | Req | Description |
|---|---|---|---|
| attachmentIndex | integer | yes | Attachment index (0-based) |
| emailId | string | yes | Email ID |
| originalBase64 | string | yes | Base64-encoded string of the original data |
No output schema declared.
No examples provided.
wait_for_email ~116
Wait until a new email matching the given criteria arrives, or until the timeout is reached. Useful for test automation after triggering an email send action.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string|null | – | Filter by sender address (case-insensitive partial match, optional) |
| subject | string|null | – | Filter by subject (case-insensitive partial match, optional) |
| timeoutSeconds | integer | – | Maximum number of seconds to wait (default: 30) |
| to | string|null | – | Filter by recipient address (case-insensitive partial match, optional) |
No output schema declared.
No examples provided.
What is the io.github.pierre3/maildev-mcp server?
io.github.pierre3/maildev-mcp is listed in the public MCP registry as io.github.pierre3/maildev-mcp. MailDev MCP server. Manage Docker containers and inspect emails from your AI editor or MCP client. This page covers its NuGet package (MailDevMcp).
Is the io.github.pierre3/maildev-mcp server safe to use?
io.github.pierre3/maildev-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 io.github.pierre3/maildev-mcp server expose?
io.github.pierre3/maildev-mcp exposes 12 tools: verify_attachment, maildev_status, delete_all_emails, delete_email, stop_maildev, and 7 more. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.
Is the io.github.pierre3/maildev-mcp server still maintained?
io.github.pierre3/maildev-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.pierre3/maildev-mcp server under?
io.github.pierre3/maildev-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.