Imap (nikolausm) MCP Server

imap-mcp-server npm v2.0.0 Source verified

Published by nikolausm — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

A powerful Model Context Protocol (MCP) server for IMAP email integration with Claude

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([imap_get_email, imap_download_attachment, imap_find_thread_messages]) co-exist with external-action tools ([imap_upload_file, imap_send_email, imap_save_draft, imap_reply_to_email, imap_forward_email]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [imap_get_email, imap_download_attachment, imap_find_thread_messages] → sinks [imap_upload_file, imap_send_email, imap_save_draft, imap_reply_to_email

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow imap_get_email → imap_upload_file

medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003

In the server's implementation (`dist/index.js:2453`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch( `https://www.ipqualityscore.com/api/json/email/${apiKey}/${encodeURIComponent(`te

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

Tools 40

Each tool and what it can reach — statically extracted from the published source.

  • imap_download_attachmentingests untrusted input
  • imap_find_thread_messagesingests untrusted input
  • imap_forward_emailnetwork egress
  • imap_get_emailingests untrusted input
  • imap_reply_to_emailnetwork egress
  • imap_save_draftnetwork egress
  • imap_send_emailnetwork egress
  • imap_upload_filenetwork egress
  • imap_add_accountno sensitive capability
  • imap_add_keywordno sensitive capability
Show 30 more tools ↓
  • imap_add_spam_domainno sensitive capability
  • imap_add_whitelist_domainno sensitive capability
  • imap_bulk_deleteno sensitive capability
  • imap_bulk_delete_by_searchno sensitive capability
  • imap_check_spamno sensitive capability
  • imap_connectno sensitive capability
  • imap_create_folderno sensitive capability
  • imap_delete_by_domainno sensitive capability
  • imap_delete_emailno sensitive capability
  • imap_delete_spamno sensitive capability
  • imap_disconnectno sensitive capability
  • imap_domain_statsno sensitive capability
  • imap_find_email_by_message_idno sensitive capability
  • imap_flag_emailno sensitive capability
  • imap_folder_statusno sensitive capability
  • imap_get_latest_emailsno sensitive capability
  • imap_get_unread_countno sensitive capability
  • imap_list_accountsno sensitive capability
  • imap_list_foldersno sensitive capability
  • imap_list_spam_domainsno sensitive capability
  • imap_mark_as_readno sensitive capability
  • imap_mark_as_unreadno sensitive capability
  • imap_move_emailno sensitive capability
  • imap_remove_accountno sensitive capability
  • imap_remove_keywordno sensitive capability
  • imap_remove_spam_domainno sensitive capability
  • imap_search_emailsno sensitive capability
  • imap_test_accountno sensitive capability
  • imap_unflag_emailno sensitive capability
  • imap_update_accountno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.0 latest A 97/100 2 1.13.0 2026-09-07
v1.6.0 A 97/100 2 1.12.1 2026-08-05
v1.5.2 A 97/100 2 1.12.1 2026-08-04

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/imap-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/imap-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/imap-mcp-server"><img src="https://mcptrustchecker.com/registry/imap-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/imap-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan imap-mcp-server --online

Use the free API → How scoring works

Other implementations of Imap 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Communication & Collaboration