Email (codefuturist) MCP Server

@codefuturist/email-mcp npm v0.2.3 Source verified

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

Email MCP server with IMAP and SMTP support.

Trust grade
B
84/100
Last scanned get badge →
Trust
B · 84/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
Critical
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
B Why this grade threat 94 − adoption risk = 84/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 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

2. Client adoption risk — 94 − 10 = 84. 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
−10 capability blast radius (critical) — 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 6

high Shell/command execution in server code (dist/cli/scheduler.js)MTC-SRC-002

In the server's implementation (`dist/cli/scheduler.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execSync } from 'node:child_process'; import fs from 'node:fs/promises'; import os from 'node:os'; import path from 'n

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/cli/scheduler.js

high Shell/command execution in server code (dist/services/local-calendar.service.js)MTC-SRC-002

In the server's implementation (`dist/services/local-calendar.service.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execFileCb } from 'node:child_process'; import { writeFile } from 'node:fs/promises'; import { tmpdir } from 'node:os';

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/services/local-calendar.service.js

high Shell/command execution in server code (dist/services/notifier.service.js)MTC-SRC-002

In the server's implementation (`dist/services/notifier.service.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from 'node:child_process'; import { mcpLog } from '../logging.js'; import { validateWebhookUrl } from '../s

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/services/notifier.service.js

high Shell/command execution in server code (dist/services/reminders.service.js)MTC-SRC-002

In the server's implementation (`dist/services/reminders.service.js:9`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: execFileCb } from 'node:child_process'; import { promisify } from 'node:util'; const execFile = promisify(execFileCb); /

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/services/reminders.service.js

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

Untrusted-input tools ([download_attachment, get_emails, mark_email]) co-exist with external-action tools ([send_email, forward_email]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [download_attachment, get_emails, mark_email] → sinks [send_email, forward_email]

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

Location: flow download_attachment → send_email

medium Untrusted input concatenated into a command sink (dist/cli/scheduler.js)MTC-SRC-009

In the server's implementation (`dist/cli/scheduler.js:112`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`launchctl load "${LAUNCHD_PLIST}"`, { stdio: 'pipe' }); } catch {

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/cli/scheduler.js

Tools 49

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

  • download_attachmentingests untrusted input
  • forward_emailnetwork egress
  • get_emailsingests untrusted input
  • mark_emailingests untrusted input
  • send_emailnetwork egress
  • add_labelno sensitive capability
  • add_to_calendarno sensitive capability
  • analyze_email_for_schedulingno sensitive capability
  • apply_templateno sensitive capability
  • bulk_actionno sensitive capability
Show 39 more tools ↓
  • cancel_scheduledno sensitive capability
  • check_calendar_permissionsno sensitive capability
  • check_healthno sensitive capability
  • check_notification_setupno sensitive capability
  • configure_alertsno sensitive capability
  • create_labelno sensitive capability
  • create_mailboxno sensitive capability
  • create_reminderno sensitive capability
  • delete_emailno sensitive capability
  • delete_labelno sensitive capability
  • delete_mailboxno sensitive capability
  • extract_calendarno sensitive capability
  • extract_contactsno sensitive capability
  • find_email_folderno sensitive capability
  • get_emailno sensitive capability
  • get_email_statsno sensitive capability
  • get_email_statusno sensitive capability
  • get_hooks_configno sensitive capability
  • get_threadno sensitive capability
  • get_watcher_statusno sensitive capability
  • list_accountsno sensitive capability
  • list_calendarsno sensitive capability
  • list_emailsno sensitive capability
  • list_eventsno sensitive capability
  • list_labelsno sensitive capability
  • list_mailboxesno sensitive capability
  • list_presetsno sensitive capability
  • list_remindersno sensitive capability
  • list_scheduledno sensitive capability
  • list_templatesno sensitive capability
  • move_emailno sensitive capability
  • remove_labelno sensitive capability
  • rename_mailboxno sensitive capability
  • reply_emailno sensitive capability
  • save_draftno sensitive capability
  • schedule_emailno sensitive capability
  • search_emailsno sensitive capability
  • send_draftno sensitive capability
  • test_notificationno 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 1

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
v0.2.3 latest B 84/100 6 1.13.0 2026-08-25

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: B · 84/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/codefuturist-email-mcp/badge.svg)](https://mcptrustchecker.com/registry/codefuturist-email-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/codefuturist-email-mcp"><img src="https://mcptrustchecker.com/registry/codefuturist-email-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/codefuturist-email-mcp/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 @codefuturist/email-mcp --online

Use the free API → How scoring works

Other implementations of Email 19

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

More in Productivity & Workflow