Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.codefuturist/email-mcp

NPM · @CODEFUTURIST/EMAIL-MCP · SCANNED AUG 10

IMAP/SMTP email MCP server — 47 tools, IMAP IDLE push, multi-account, AI triage.

+4 this week 29 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects nodemailer 8.0.11, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 37 of 132 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
  • Clear OSI-approved license (LGPL-3.0-or-later).Pass
  • Actively maintained (last published 85 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @codefuturist/email-mcp

# add to Claude Code
claude mcp add codefuturist-email-mcp -- npx -y @codefuturist/email-mcp
# add to Codex CLI
codex mcp add codefuturist-email-mcp -- npx -y @codefuturist/email-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "codefuturist-email-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@codefuturist/email-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add codefuturist-email-mcp --command npx --arg -y --arg @codefuturist/email-mcp
# ~/.hermes/config.yaml
mcp_servers:
  codefuturist-email-mcp:
    command: "npx"
    args: ["-y", "@codefuturist/email-mcp"]
// mcp.json
{
  "mcpServers": {
    "codefuturist-email-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@codefuturist/email-mcp"
      ]
    }
  }
}
Changelog

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.

  • 8 Aug 26 +4
    • Security disclosure: fail → pass functional
    • Dependency health: partial → 0.88 functional
  • 2 Aug 26 +25
    • GHSA-p6gq-j5cr-w38f affects this package: high security
    • Known CVEs: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Provenance: Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. security
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • Licence: LGPL-3.0-or-later functional
  • 1 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
  • 27 Jul 26 18

    First indexed and scored.

Diagnostics

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 10 Aug 2026 · Analysed npm/@codefuturist/[email protected]

Provenance Repository mismatch

The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.

Result Repository mismatch
Ecosystem npm
Reason Repository mismatch
Discovered via Registry attestation endpoint
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/codefuturist/shared-workflows/.github/workflows/release-npm.yml@refs/tags/v1
Rekor log index 1553615037
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:27d7c6fc7099d0a8b1cb9937dba5870dfbcf395f52e114cefb1494e6fbdf10770e7d89078997d0cf8751c7ec4183e41a38ae5baa2b0a5bea4210d09f4
Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-p6gq-j5cr-w38f high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
Dependencies 132 packages
Packages resolved 132
Stale 37
Tree resolution Complete
MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.