titan-email-mcp

MCPcommunity
v1.0.5qmmughalMITUpdated 4d agonpmGitHub

MCP server that connects Claude (or any MCP client) to a Titan Email mailbox over IMAP/SMTP, tested and confirmed with GoDaddy mailboxes.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1kDownloads/wk
4d agoLast update
Needs 1 credential before it runs
  • TITAN_PASSWORDAPI keyrequired

    Your Titan Email password (use an app-specific password if your provider offers one)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorqmmughal
LicenseMIT
Version1.0.5
Sourcenpm+mcp-registry
npmtitan-email-mcp
GitHubqmmughal/titan-email-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · 1 privileged
Security scan✓ Cleanv1.0.5 · todayHow well does this scan work?
EvalsNone
IndexedOct 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · 1 privileged
Statically extracted from the published packagev1.0.5 · 23h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

test_connectionVerify IMAP and SMTP login against the configured Titan (or GoDaddy-hosted Titan) account.

Verify IMAP and SMTP login against the configured Titan (or GoDaddy-hosted Titan) account.

No input schema was published for this tool.

list_foldersList all mailbox folders with message and unread counts.

List all mailbox folders with message and unread counts.

No input schema was published for this tool.

list_emailsList the most recent emails in a folder (newest first).

List the most recent emails in a folder (newest first).

No input schema was published for this tool.

search_emailsSearch a folder by sender, recipient, subject, body text, date range or read state.

Search a folder by sender, recipient, subject, body text, date range or read state.

No input schema was published for this tool.

read_emailRead a full email by UID: headers, plain-text body and attachment list.

Read a full email by UID: headers, plain-text body and attachment list.

No input schema was published for this tool.

send_emailSend a new email from the Titan account. A copy is saved to the Sent folder.

Send a new email from the Titan account. A copy is saved to the Sent folder.

No input schema was published for this tool.

reply_emailReply to an email by UID, threading it correctly. Set reply_all to include all recipients.

Reply to an email by UID, threading it correctly. Set reply_all to include all recipients.

No input schema was published for this tool.

save_draftSave an email to the Drafts folder without sending it.

Save an email to the Drafts folder without sending it.

No input schema was published for this tool.

move_emailprivilegedMove emails to another folder (e.g. Archive, Trash).

Move emails to another folder (e.g. Archive, Trash).

No input schema was published for this tool.

set_flagsMark emails read/unread and flagged/unflagged.

Mark emails read/unread and flagged/unflagged.

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server that connects Claude (or any MCP client) to a Titan Email mailbox over IMAP/SMTP, tested and confirmed with GoDaddy mailboxes.

Keywords
mcpmodel-context-protocoltitan-emailtitangodaddyemailimapsmtpclaudeclaude-desktopclaude-codeai-agent
Alternatives
Comparing tool surfaces…

Tools exposed

10 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-15 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in email