← Index

Email (IMAP/SMTP)

io.github.mindstone/mcp-server-email-imapv0.3.2Email

Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers

The current version, v0.3.2, was published to the official MCP registry on 2026-08-10. It is distributed as @mindstone/mcp-server-email-imap on npm, filed under Email by this index, and declares 11 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Email (IMAP/SMTP) in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-09-04 06:08 UTC
screened 2026-07-06tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidenceNo malicious instructions foundvia static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-08-28).

Contracts can change after screening, with no version bump. The gate pins Email (IMAP/SMTP)’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Email (IMAP/SMTP)](https://mcpindex.ai/server/io-github-mindstone-mcp-server-email-imap) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-mindstone-mcp-server-email-imap">Independent trust record for Email (IMAP/SMTP)</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-mindstone-mcp-server-email-imap)](https://mcpindex.ai/server/io-github-mindstone-mcp-server-email-imap)
HTML
<a href="https://mcpindex.ai/server/io-github-mindstone-mcp-server-email-imap"><img src="https://mcpindex.ai/api/v1/badge/io-github-mindstone-mcp-server-email-imap" alt="mcpindex verdict" height="20" /></a>
Environment variables
EMAIL_IMAP_EMAIL
required

Email address

EMAIL_IMAP_PASSWORD
requiredsecret

App-specific password

EMAIL_IMAP_PROVIDER

Provider — icloud, gmail, yahoo, outlook, or custom (auto-detected from email domain if unset)

EMAIL_IMAP_IMAP_HOST

Custom IMAP host (for provider=custom)

EMAIL_IMAP_SMTP_HOST

Custom SMTP host (for provider=custom)

EMAIL_IMAP_IMAP_PORT

Custom IMAP port

EMAIL_IMAP_SMTP_PORT

Custom SMTP port

EMAIL_IMAP_MAX_RECIPIENTS

Safety cap: maximum combined To+CC+BCC recipients per email_send call. Defaults to 25; raising bypasses spam-prevention guardrails against prompt-injection-driven mass sends.

EMAIL_IMAP_RATE_LIMIT_PER_HOUR

Safety cap: maximum email_send calls per rolling window. Defaults to 50; protects against runaway sends when injection content escapes the LLM's intent.

EMAIL_IMAP_RATE_LIMIT_WINDOW_MS

Sliding-window length for the rate limit (ms)

MCP_WORKSPACE_PATH

Workspace directory that email_get_attachment downloads into (fresh email-imap-attachment-* staging directories). Defaults to the system temp directory.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
15
installability
25
documentation
15
stability
5
Alternatives in Email