io.github.infoinlet-marketplace/mcp-email
NPM · @INFOINLET/MCP-EMAIL
Email for AI agents — read inbox (IMAP), search, and send (SMTP).
Available components
Last scanned (18 hours ago)
Scores higher than 32% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects nodemailer 6.10.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 36 of 142 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 158 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 165 tokens (~41/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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; "send_email" 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 4 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
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.
- 4 Nov 26 −5
- CVE-2026-121426 affects this package: high ▼ security
- CVE-2026-121424 affects this package: high ▼ security
- CVE-2026-121425 affects this package: high ▼ security
- GHSA-8c8m-p3m8-cjg8 no longer affects this package ▲ security
- GHSA-85x2-q946-cp5h no longer affects this package ▲ security
- GHSA-m943-m63m-w62w no longer affects this package ▲ security
- Stability: pass → 0.63 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- CVE-2026-110869 affects this package: high ▼ security
- CVE-2026-110872 affects this package: high ▼ security
- CVE-2026-110870 affects this package: high ▼ security
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- GHSA-85x2-q946-cp5h affects this package: high ▼ security
- GHSA-m943-m63m-w62w affects this package: high ▼ security
- GHSA-8c8m-p3m8-cjg8 affects this package: high ▼ security
- 23 Oct 26 0
- CVE-2026-110871 affects this package: high ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.80 → pass security
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 npm/@infoinlet/mcp-email@0.1.1
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 →
Vulnerabilities 22 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-268h-hp4c-crq3 | CVE-2026-82661 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-2x7j-588g-ccc2 | CVE-2026-92596 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-39m8-27wv-hr27 | CVE-2026-110871 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-4ffr-jq9g-5ffx | CVE-2026-110869 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-4g23-2xm8-66gc | CVE-2026-110872 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6vj9-mwq6-2f5v | CVE-2026-100701 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-85x2-q946-cp5h | CVE-2026-121426 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-8c8m-p3m8-cjg8 | CVE-2026-121424 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-8m3c-c648-2xjj | CVE-2026-92595 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-8vvx-rff5-p5rq | CVE-2026-100702 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-c7w3-x93f-qmm8 | CVE-2026-82854 | low | yes | |
| GHSA-cc9r-2j5m-2m83 | CVE-2026-92597 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-g73g-hqqh-jr95 | CVE-2026-110870 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-m943-m63m-w62w | CVE-2026-121425 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-mm7p-fcc7-pg87 | CVE-2025-13033 | medium | yes | |
| GHSA-p6gq-j5cr-w38f | CVE-2026-82659 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-r7g4-qg5f-qqm2 | CVE-2026-82662 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-rcmh-qjqh-p98v | CVE-2025-14874 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-v53p-9fqp-m79j | CVE-2026-100700 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vvjj-xcjg-gr5g | CVE-2026-82853 | medium | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-wmmp-3585-3rmp | CVE-2026-92598 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-wqvq-jvpq-h66f | CVE-2026-82660 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 142 packages
| Packages resolved | 142 |
|---|---|
| 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 →
list_messages ~31
List the most recent inbox messages (IMAP). Requires IMAP_* config.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
No output schema declared.
No examples provided.
read_message ~27
Read a message by UID (subject/from/to/date/text).
| Name | Type | Req | Description |
|---|---|---|---|
| uid | number | yes | – |
No output schema declared.
No examples provided.
search_messages ~49
Search the inbox by from / subject / since (ISO date).
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| from | string | – | – |
| since | string | – | – |
| subject | string | – | – |
No output schema declared.
No examples provided.
send_email ~58
Send an email (SMTP). `to` may be a comma/semicolon list. Requires SMTP_* config.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | – |
| subject | string | yes | – |
| text | string | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.infoinlet-marketplace/mcp-email server?
io.github.infoinlet-marketplace/mcp-email runs locally as an npm package, launched with npx -y @infoinlet/mcp-email. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @infoinlet/mcp-email
claude mcp add infoinlet-marketplace-mcp-email -- npx -y @infoinlet/mcp-email
What is the io.github.infoinlet-marketplace/mcp-email server?
io.github.infoinlet-marketplace/mcp-email is listed in the public MCP registry as io.github.infoinlet-marketplace/mcp-email. Email for AI agents, read inbox (IMAP), search, and send (SMTP). This page covers its npm package (@infoinlet/mcp-email).
Is the io.github.infoinlet-marketplace/mcp-email server safe to use?
io.github.infoinlet-marketplace/mcp-email scores 63 out of 100 on VerifyMCP. We recorded 22 known advisories against 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 io.github.infoinlet-marketplace/mcp-email server expose?
io.github.infoinlet-marketplace/mcp-email exposes 4 tools: list_messages, read_message, search_messages, send_email. Their descriptions and schemas cost roughly 165 tokens of context every time the server is loaded.
Is the io.github.infoinlet-marketplace/mcp-email server still maintained?
io.github.infoinlet-marketplace/mcp-email 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 io.github.infoinlet-marketplace/mcp-email server under?
io.github.infoinlet-marketplace/mcp-email declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.