io.github.qmmughal/titan-email-mcp
NPM · TITAN-EMAIL-MCP
MCP server for Titan Email (IMAP/SMTP), tested and confirmed with GoDaddy mailboxes.
Available components
Last scanned (1 hour ago)
Scores higher than 37% 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
- 36 of 136 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 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 654 tokens (~65/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
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 10 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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +3
- Stability: unverified → 0.27 ▲ functional
- 16 Oct 26 +1
No change was recorded against any check on this day. Supply Chain Security went from 98 to 99.
- 14 Oct 26 +26
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Tool coverage: 35 functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- 12 Oct 26 38
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 24 Oct 2026 · Analysed npm/titan-email-mcp@1.0.5
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 136 packages
| Packages resolved | 136 |
|---|---|
| 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_emails ~57
List the most recent emails in a folder (newest first).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Mailbox path, e.g. INBOX, Sent, Archive |
| limit | integer | – | – |
| unread_only | boolean | – | – |
No output schema declared.
No examples provided.
list_folders ~19
List all mailbox folders with message and unread counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
move_email ~56
Move emails to another folder (e.g. Archive, Trash).
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| folder | string | – | Mailbox path, e.g. INBOX, Sent, Archive |
| uids | array | yes | – |
No output schema declared.
No examples provided.
read_email ~67
Read a full email by UID: headers, plain-text body and attachment list.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Mailbox path, e.g. INBOX, Sent, Archive |
| mark_read | boolean | – | – |
| max_chars | integer | – | – |
| uid | integer | yes | – |
No output schema declared.
No examples provided.
reply_email ~83
Reply to an email by UID, threading it correctly. Set reply_all to include all recipients.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| draft_only | boolean | – | Save as draft instead of sending |
| folder | string | – | Mailbox path, e.g. INBOX, Sent, Archive |
| reply_all | boolean | – | – |
| uid | integer | yes | – |
No output schema declared.
No examples provided.
save_draft ~70
Save an email to the Drafts folder without sending it.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | array | – | – |
| body | string | yes | Plain-text body |
| cc | array | – | – |
| html | string | – | Optional HTML body |
| subject | string | yes | – |
| to | array | yes | – |
No output schema declared.
No examples provided.
search_emails ~117
Search a folder by sender, recipient, subject, body text, date range or read state.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | ISO date, exclusive |
| folder | string | – | Mailbox path, e.g. INBOX, Sent, Archive |
| from | string | – | – |
| limit | integer | – | – |
| since | string | – | ISO date, inclusive |
| subject | string | – | – |
| text | string | – | Matches headers or body |
| to | string | – | – |
| unread_only | boolean | – | – |
No output schema declared.
No examples provided.
send_email ~75
Send a new email from the Titan account. A copy is saved to the Sent folder.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | array | – | – |
| body | string | yes | Plain-text body |
| cc | array | – | – |
| html | string | – | Optional HTML body |
| subject | string | yes | – |
| to | array | yes | – |
No output schema declared.
No examples provided.
set_flags ~61
Mark emails read/unread and flagged/unflagged.
| Name | Type | Req | Description |
|---|---|---|---|
| flagged | boolean | – | – |
| folder | string | – | Mailbox path, e.g. INBOX, Sent, Archive |
| read | boolean | – | – |
| uids | array | yes | – |
No output schema declared.
No examples provided.
test_connection ~49
Verify IMAP and SMTP login against the configured Titan (or GoDaddy-hosted Titan) account. Run this first after setup — it touches no mail, it only confirms the credentials and host settings work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.qmmughal/titan-email-mcp server?
io.github.qmmughal/titan-email-mcp runs locally as an npm package, launched with npx -y titan-email-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 · titan-email-mcp
claude mcp add qmmughal-titan-email-mcp -- npx -y titan-email-mcp
What is the io.github.qmmughal/titan-email-mcp server?
io.github.qmmughal/titan-email-mcp is listed in the public MCP registry as io.github.qmmughal/titan-email-mcp. MCP server for Titan Email (IMAP/SMTP), tested and confirmed with GoDaddy mailboxes. This page covers its npm package (titan-email-mcp).
Is the io.github.qmmughal/titan-email-mcp server safe to use?
io.github.qmmughal/titan-email-mcp scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 October 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.qmmughal/titan-email-mcp server expose?
io.github.qmmughal/titan-email-mcp exposes 10 tools: test_connection, list_folders, list_emails, search_emails, read_email, and 5 more. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.
Is the io.github.qmmughal/titan-email-mcp server still maintained?
io.github.qmmughal/titan-email-mcp is still listed as active in the MCP registry. We last reached this channel on 24 October 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.qmmughal/titan-email-mcp server under?
io.github.qmmughal/titan-email-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.