io.github.samihalawa/email-smtp-imap-mcp
NPM · EMAIL-SMTP-IMAP-MCP
Multi-account SMTP/IMAP email tools: search, read, send, reply, forward, flags and folders.
Available components
Last scanned (14 hours ago)
Scores higher than 72% of npm servers
Category Communication
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 Security99
- 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 141 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to samihalawa/email-smtp-imap-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 786 tokens (~131/item across 6 items; 6 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 Management17
- Stability observed for 5 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "email_send" implies "send" 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 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Stability: unverified → 0.10 ▲ functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 65
First indexed and scored.
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 5 Nov 2026 · Analysed npm/email-smtp-imap-mcp@2.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | samihalawa/email-smtp-imap-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/samihalawa/email-smtp-imap-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3614804278 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cda16b13b7398d118ca0cb7f76d7c4cc879589fbb436fb6bc783e928a40eb5bbe2bc479fde080ed039c58dc06f29220a2898d1385721a1bd0d71b7611 |
Background: How many MCP packages publish verified provenance →
Dependencies 141 packages
| Packages resolved | 141 |
|---|---|
| Stale | 36 |
| 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 →
accounts_list ~36
List every configured email account and show which account is the default. Use this before other tools when multiple SMTP/IMAP accounts are configured.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
email_respond ~189
Reply to or forward an existing email. Use this to continue email conversations, respond to messages, or forward information to others.
| Name | Type | Req | Description |
|---|---|---|---|
| account_name | string | – | Name of the email account to use |
| additional_attachments | array | – | Additional attachments to include |
| body | string | yes | Your response message content |
| body_type | string | – | Response body format |
| email_id | string | yes | ID of the email to respond to (from emails_find results) |
| include_attachments | boolean | – | Include attachments from the original email |
| include_original | boolean | – | Include the original email content in your response |
| response_type | string | – | 'reply' to sender only, 'reply_all' to all recipients, or 'forward' to new recipients |
| to | array | – | Array of recipient emails (required for 'forward', optional for replies to override default recipients) |
No output schema declared.
No examples provided.
email_send ~181
Send a new email with HTML support and file attachments. Use this to send messages, project updates, or any new email conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| account_name | string | – | Name of the email account to use |
| attachments | array | – | Array of file attachments |
| bcc | array | – | Array of BCC recipient email addresses |
| body | string | yes | Email body content (can be plain text or HTML) |
| body_type | string | – | Body format: 'plain' for plain text or 'html' for HTML content |
| cc | array | – | Array of CC recipient email addresses |
| from_email | string | – | Optional sender address. When sender_emails is configured for the account, the address must be in that allowlist. |
| subject | string | yes | Email subject line |
| to | array | yes | Array of recipient email addresses |
No output schema declared.
No examples provided.
emails_find ~164
Search for emails in your inbox with flexible filters. Optionally get full email content and attachments. Use this to find specific emails, check for unread messages, or browse your inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| account_name | string | – | Name of the email account to use (e.g., 'work', 'personal'). If not provided, uses the default account. |
| filters | object | – | Structured filters for precise email search |
| include_attachments | boolean | – | Include attachment content (base64 encoded) |
| include_content | boolean | – | Include full email body content in results |
| limit | number | – | Maximum number of emails to return (1-100) |
| query | string | – | Text to search across subject, body, sender, and recipients (e.g., 'project update') |
No output schema declared.
No examples provided.
emails_modify ~154
Change email states like read/unread, flagged, or move between folders. Use this to organize your inbox, mark emails as read, archive messages, or flag important emails.
| Name | Type | Req | Description |
|---|---|---|---|
| account_name | string | – | Name of the email account to use |
| email_ids | array | yes | Array of email IDs to modify (from emails_find results) |
| flag | boolean | – | Flag/star emails as important |
| mark_read | boolean | – | Mark emails as read |
| mark_unread | boolean | – | Mark emails as unread |
| move_to_folder | string | – | Move emails to a folder (e.g., 'Archive', 'Trash', 'INBOX') |
| unflag | boolean | – | Remove flag/star from emails |
No output schema declared.
No examples provided.
folders_list ~62
List all available email folders/labels in your account. Use this to see your folder structure and organize emails.
| Name | Type | Req | Description |
|---|---|---|---|
| account_name | string | – | Name of the email account to use |
| include_counts | boolean | – | Include unread and total message counts for each folder |
No output schema declared.
No examples provided.
How do I install the io.github.samihalawa/email-smtp-imap-mcp server?
io.github.samihalawa/email-smtp-imap-mcp runs locally as an npm package, launched with npx -y email-smtp-imap-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · email-smtp-imap-mcp
claude mcp add samihalawa-email-smtp-imap-mcp -- npx -y email-smtp-imap-mcp
What is the io.github.samihalawa/email-smtp-imap-mcp server?
io.github.samihalawa/email-smtp-imap-mcp is listed in the public MCP registry as io.github.samihalawa/email-smtp-imap-mcp. Multi-account SMTP/IMAP email tools: search, read, send, reply, forward, flags and folders. This page covers its npm package (email-smtp-imap-mcp).
Is the io.github.samihalawa/email-smtp-imap-mcp server safe to use?
io.github.samihalawa/email-smtp-imap-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.samihalawa/email-smtp-imap-mcp server expose?
io.github.samihalawa/email-smtp-imap-mcp exposes 6 tools: accounts_list, emails_find, emails_modify, email_send, email_respond, folders_list. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.
Is the io.github.samihalawa/email-smtp-imap-mcp server still maintained?
io.github.samihalawa/email-smtp-imap-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.samihalawa/email-smtp-imap-mcp server under?
io.github.samihalawa/email-smtp-imap-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.
What did VerifyMCP test on the io.github.samihalawa/email-smtp-imap-mcp server?
VerifyMCP ran 16 checks on io.github.samihalawa/email-smtp-imap-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.