Lettio MCP
NPM · @LETTIO/MCP · 2 COMPONENTS
Private, EU-hosted email for AI agents over JMAP: read, search, reply, draft, organize, send.
Available components
Last scanned (16 hours ago)
Scores higher than 53% 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 zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
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 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2184 tokens (~109/item across 20 items; 20 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 Management85
- Stability check failed: the tool surface changed between 0.1.2 and 0.5.0: 0 tool removals, 3 breaking changes, 10 additions. See how to fix → Fail
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 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.
- 10 Nov 26 +5
- Source repository: unverified → pass ▲ security
- 9 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 78 to 82.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 68 to 72.
- 4 Nov 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 85 to 68.
- 3 Nov 26 +20
- Known CVEs: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → 0.86 ▲ functional
- 2 Nov 26 −23
- Malware scan: pass → unverified ▼ security
- Known CVEs: fail → unverified ▼ security
- Stability: pass → fail ▼ security
- Dependency health: 0.85 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Schema quality: excellent → good functional
- Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Package version: 0.1.2 → 0.5.0 functional
- 29 Oct 26 +1
- Stability: 0.97 → 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 21 Nov 2026 · Analysed npm/@lettio/mcp@0.5.0
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| 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 →
create_draft ~220
Save a new message to Drafts without sending it.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| attachments | array | – | Files to attach. Give content_base64, or from_email_id with attachment_id. |
| bcc | array | – | Bcc recipients. |
| body | string | yes | The message in Markdown. Supports headings, bold, lists, tables, `> quote` (end with `> — Name` for attribution), callouts `> [!NOTE] Title`, code blocks, and buttons `[Label](https://url "button")`.… |
| cc | array | – | Cc recipients. |
| format | string | – | "plain" sends text as written, without formatting. |
| signature | boolean | – | Append the mailbox signature. Default true; don't write a sign-off block yourself. |
| subject | string | yes | Subject line. |
| to | array | yes | Recipient email addresses. |
No output schema declared.
No examples provided.
create_folder ~69
Create a mail folder, optionally inside another.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| name | string | yes | Folder name. |
| parent | string | – | Parent folder role or name. |
No output schema declared.
No examples provided.
create_reply_draft ~216
Save a reply to Drafts, in the same conversation, without sending it.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| attachments | array | – | Files to attach. Give content_base64, or from_email_id with attachment_id. |
| body | string | yes | The message in Markdown. Supports headings, bold, lists, tables, `> quote` (end with `> — Name` for attribution), callouts `> [!NOTE] Title`, code blocks, and buttons `[Label](https://url "button")`.… |
| format | string | – | "plain" sends text as written, without formatting. |
| id | string | yes | The id of the email to reply to. |
| reply_all | boolean | – | Also Cc everyone on the original. |
| signature | boolean | – | Append the mailbox signature. Default true; don't write a sign-off block yourself. |
No output schema declared.
No examples provided.
flag_email ~76
Flag (star) or unflag emails.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| flagged | boolean | yes | true to flag, false to remove the flag. |
| ids | array | yes | One or more email ids. |
No output schema declared.
No examples provided.
get_attachment ~118
Open an attachment. Text and PDF come back as text, images as images, other files as a binary resource. Give save_to to write it to a local file instead.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| attachment_id | string | yes | The attachment_id shown by read_email. |
| email_id | string | yes | The email the attachment belongs to. |
| save_to | string | – | Local path to save the file to. |
No output schema declared.
No examples provided.
get_signature ~49
Show the signature that is added to outgoing mail.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
No output schema declared.
No examples provided.
get_thread ~64
Read the whole conversation an email belongs to, oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| id | string | yes | Any email id in the thread. |
No output schema declared.
No examples provided.
label_email ~92
Add or remove a label on emails.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| add | boolean | – | false removes the label. Default true. |
| ids | array | yes | One or more email ids. |
| label | string | yes | Label name: letters, digits, dot, dash or underscore. |
No output schema declared.
No examples provided.
list_accounts ~17
List the mailboxes this server can use.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_mailboxes ~48
List folders with message and unread counts.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
No output schema declared.
No examples provided.
list_recent_emails ~106
List the most recent emails in a folder, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| limit | integer | – | How many (default 10). |
| mailbox | string | – | Folder role or name. Default "inbox". |
| offset | integer | – | Skip this many, for paging. |
| unread_only | boolean | – | Only unread messages. |
No output schema declared.
No examples provided.
move_email ~89
Move emails to a folder. Use "archive", "trash" (reversible), "inbox", or a folder name.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| ids | array | yes | One or more email ids. |
| mailbox | string | yes | Target folder role or name. |
No output schema declared.
No examples provided.
read_email ~68
Read one email: its text and a list of attachments. HTML mail is converted to text.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| id | string | yes | The email id. |
No output schema declared.
No examples provided.
reply_email ~219
Reply in the same conversation and send it. Replies to the sender, or to everyone with reply_all.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| attachments | array | – | Files to attach. Give content_base64, or from_email_id with attachment_id. |
| body | string | yes | The message in Markdown. Supports headings, bold, lists, tables, `> quote` (end with `> — Name` for attribution), callouts `> [!NOTE] Title`, code blocks, and buttons `[Label](https://url "button")`.… |
| format | string | – | "plain" sends text as written, without formatting. |
| id | string | yes | The id of the email to reply to. |
| reply_all | boolean | – | Also Cc everyone on the original. |
| signature | boolean | – | Append the mailbox signature. Default true; don't write a sign-off block yourself. |
No output schema declared.
No examples provided.
search_emails ~206
Search email. Combine free text with filters; all given filters must match. With several mailboxes and no account, searches them all.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| after | string | – | Received after this date, e.g. 2026-10-01. |
| before | string | – | Received before this date. |
| from | string | – | Sender contains. |
| has_attachment | boolean | – | Only with, or only without, attachments. |
| limit | integer | – | How many (default 10). |
| mailbox | string | – | Limit to one folder. |
| offset | integer | – | Skip this many, for paging. |
| query | string | – | Free text across sender, subject and body. |
| subject | string | – | Subject contains. |
| to | string | – | Recipient contains. |
| unread_only | boolean | – | Only unread messages. |
No output schema declared.
No examples provided.
send_draft ~66
Send a draft that is already in Drafts. This really sends.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| id | string | yes | The draft's email id. |
No output schema declared.
No examples provided.
send_email ~241
Send an email from this mailbox. This really sends, and the sender is always this mailbox. Write in Markdown; recipients get formatted HTML with a plain-text version.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| attachments | array | – | Files to attach. Give content_base64, or from_email_id with attachment_id. |
| bcc | array | – | Bcc recipients. |
| body | string | yes | The message in Markdown. Supports headings, bold, lists, tables, `> quote` (end with `> — Name` for attribution), callouts `> [!NOTE] Title`, code blocks, and buttons `[Label](https://url "button")`.… |
| cc | array | – | Cc recipients. |
| format | string | – | "plain" sends text as written, without formatting. |
| signature | boolean | – | Append the mailbox signature. Default true; don't write a sign-off block yourself. |
| subject | string | yes | Subject line. |
| to | array | yes | Recipient email addresses. |
No output schema declared.
No examples provided.
set_read_status ~72
Mark emails read or unread.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| ids | array | yes | One or more email ids. |
| read | boolean | yes | true for read, false for unread. |
No output schema declared.
No examples provided.
set_signature ~97
Set the signature added to outgoing mail. Stored on the mailbox, so it applies to every client that reads it.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
| html | string | – | Optional HTML version. Built from the text when omitted. |
| text | string | yes | Plain-text signature, one item per line, name first. |
No output schema declared.
No examples provided.
whoami ~51
Show which mailbox this connection uses and whether it may send.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Which mailbox to use. Defaults to the first. Pass the Mailbox shown in a list result when acting on that email. |
No output schema declared.
No examples provided.
How do I install the Lettio MCP server?
Lettio MCP runs locally as an npm package, launched with npx -y @lettio/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 · @lettio/mcp
claude mcp add eu-lettio-mcp -- npx -y @lettio/mcp
What is the Lettio MCP server?
Lettio MCP is listed in the public MCP registry as eu.lettio/mcp. Private, EU-hosted email for AI agents over JMAP: read, search, reply, draft, organize, send. This page covers its npm package (@lettio/mcp).
Is the Lettio MCP server safe to use?
Lettio MCP scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 Lettio MCP server expose?
Lettio MCP exposes 20 tools: whoami, list_accounts, list_mailboxes, list_recent_emails, search_emails, and 15 more. Their descriptions and schemas cost roughly 2,184 tokens of context every time the server is loaded.
Is the Lettio MCP server still maintained?
Lettio MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 Lettio MCP server under?
Lettio 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 Lettio MCP server?
VerifyMCP ran 16 checks on Lettio 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.