Is io.github.Temple-of-Epiphany/imap-mcp-pro safe to use?

io.github.Temple-of-Epiphany/imap-mcp-pro has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.Temple-of-Epiphany/imap-mcp-pro?

io.github.Temple-of-Epiphany/imap-mcp-pro supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.Temple-of-Epiphany/imap-mcp-pro?

io.github.Temple-of-Epiphany/imap-mcp-pro is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.Temple-of-Epiphany/imap-mcp-pro actively maintained?

io.github.Temple-of-Epiphany/imap-mcp-pro is actively maintained — last commit was 7 days ago.

io.github.Temple-of-Epiphany/imap-mcp-pro

npm

Production IMAP & SMTP for Claude: multi-account email search, triage, send, and spam checks.

14.9M/wk GitHub npm

No known CVEs

No license

Actively maintained

Last commit 7d ago

Works with most clients

Transport: stdio, sse, http

0 tools

Grade F

Edit this pageView history

AI / ML Communication

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "imap-customer-a": {
      "env": {
        "MCP_USER_ID": "customer-a"
      }
    },
    "imap-customer-b": {
      "env": {
        "MCP_USER_ID": "customer-b"
      }
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-temple-of-epiphany-imap-mcp-pro)](https://mcppedia.org/s/io-github-temple-of-epiphany-imap-mcp-pro)

Read me

What io.github.Temple-of-Epiphany/imap-mcp-pro does

An enterprise-grade Model Context Protocol (MCP) server that provides production-ready IMAP email integration with advanced reliability features, comprehensive monitoring, and secure account management.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

60/100across 5 weighted dimensions

How we score →

0255075100

−40

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Temple-of-Epiphany/imap-mcp-pro safe to use?: io.github.Temple-of-Epiphany/imap-mcp-pro has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.Temple-of-Epiphany/imap-mcp-pro?: io.github.Temple-of-Epiphany/imap-mcp-pro supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.Temple-of-Epiphany/imap-mcp-pro?: io.github.Temple-of-Epiphany/imap-mcp-pro is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.Temple-of-Epiphany/imap-mcp-pro actively maintained?: io.github.Temple-of-Epiphany/imap-mcp-pro is actively maintained — last commit was 7 days ago.

Similar servers

Others in ai-ml / communication

View all →

Sequential Thinking MCP Server98

Dynamic problem-solving through sequential thought chains

87.9k 1

Memory MCP Server98

Persistent memory using a knowledge graph

87.9k 5

Mcp_agent_mail96

Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite

2.0k 6

Gpt Researcher95

An autonomous agent that conducts deep research on any data using any LLM providers

28.0k 5

MCP Security Weekly

Get CVE alerts and security updates for io.github.Temple-of-Epiphany/imap-mcp-pro and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

AI / ML Communication

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "imap-customer-a": {
      "env": {
        "MCP_USER_ID": "customer-a"
      }
    },
    "imap-customer-b": {
      "env": {
        "MCP_USER_ID": "customer-b"
      }
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-temple-of-epiphany-imap-mcp-pro)](https://mcppedia.org/s/io-github-temple-of-epiphany-imap-mcp-pro)

Read me

What io.github.Temple-of-Epiphany/imap-mcp-pro does

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

IMAP MCP Pro

Professional Edition — Enhanced fork with Level 1-3 reliability features, circuit breaker pattern, metrics, and bulk operations for commercial and large-scale deployments.

📜 License at a glance

Free for personal, educational, and non-profit use. Paid commercial license required for any business, SaaS, revenue-generating, or multi-tenant deployment.

Contact for commercial licensing: colin.bitterfield@templeofepiphany.com Full terms: LICENSE · License section below

Features

100+ MCP tools across email/folder/account/category/scoring/subscription/dns-firewall/usercheck/staging/cache/diagnostics — every IMAP4rev2 (RFC 9051) operation we use is exposed. See the full categorized list with exact count in docs/TOOL_CATALOG.md (generated from the manifest on every build), or run imap_list_tools for the live catalog at runtime.

Core Features

🔐 Secure Account Management: Encrypted credential storage with AES-256 encryption
🚀 Connection Pooling: Efficient IMAP connection management
📧 Comprehensive Email Operations: Search, read, mark, delete emails
✉️ Email Sending: Send, reply, and forward emails via SMTP
📁 Folder Management: List folders, check status, get unread counts
🔄 Multiple Account Support: Manage multiple IMAP accounts simultaneously
🛡️ Type-Safe: Built with TypeScript for reliability
🌐 Web-Based Setup Wizard: Easy account configuration with provider presets
📱 15+ Email Providers: Pre-configured settings for Gmail, Outlook, Yahoo, and more
🔗 Auto SMTP Configuration: Automatic SMTP settings based on IMAP provider

Local Message Cache + Auto-installed Skills (v2.17.0+)

Local SQLite header cache for fast sender enumeration. imap_sync_folder_cache populates a per-folder cache; imap_search_cache runs group_by_sender / by_domain / by_address queries against it in milliseconds. Validated end-to-end against a 1500-message INBOX: cold sync 1.7s, warm group-by-sender 4ms.
UIDVALIDITY-aware delta sync: subsequent syncs only fetch new UIDs. Mailbox renumbering is detected automatically and triggers a full resync.
Cache-miss is explicit: imap_search_cache returns a structured cache_miss error when a folder has not been synced — no silent IMAP fallback. The skill orchestrates the order.
Auto-installed skills: bundled Claude skills (unsubscribe-cleanup in v2.17.0) are copied to ~/.claude/skills/imap-mcp-pro/ on server startup. Idempotent: skips when versions match, updates when the bundle is newer, preserves on-disk content with a higher version. Disable via IMAP_MCP_SKIP_SKILLS_INSTALL=1.
Skill updates from public GitHub (v2.17.4+): two new tools, imap_check_skill_updates and imap_update_skills, let you pull newer skill versions from this repo without reinstalling the .mcpb. No PAT needed — the default source is the MCP's own public repo. See docs/SKILLS.md for the full guide including the trust model.

v2.0 Reliability & Attachments (v2.15.0+)

Auto-Sent-folder placement: every imap_send_email archives to the right Sent folder by provider (Gmail / Outlook / iCloud / Fastmail / Yahoo / Hostinger / Zoho / GMX / ProtonMail). Bcc preserved in the archive copy per RFC 5322 §3.6.3. Failures queue for background retry, not lost.
**Pooled SMTP with classified

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

60/100across 5 weighted dimensions

How we score →

0255075100

−40

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Affected: >= 0Fixed in 6.13.4source →

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Temple-of-Epiphany/imap-mcp-pro safe to use?: io.github.Temple-of-Epiphany/imap-mcp-pro has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.Temple-of-Epiphany/imap-mcp-pro?: io.github.Temple-of-Epiphany/imap-mcp-pro supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.Temple-of-Epiphany/imap-mcp-pro?: io.github.Temple-of-Epiphany/imap-mcp-pro is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.Temple-of-Epiphany/imap-mcp-pro actively maintained?: io.github.Temple-of-Epiphany/imap-mcp-pro is actively maintained — last commit was 7 days ago.