Apple Mail (egorkurito) MCP Server
@egorkurito/apple-mail-mcp
npm
v1.0.0
Published by @egorkurito — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Apple Mail via NSAppleScript
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 92. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 3
high Shell/command execution in server code (build/bridge/swift.js)MTC-SRC-002
In the server's implementation (`build/bridge/swift.js:23`): 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: nary(); } async exec(args) { const result = await execa(this.binPath, args, { reject: false,
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 build/bridge/swift.js
low Shell/command execution in packaging/dev tooling (scripts/postinstall.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/postinstall.js:1`): 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 { existsSync } from "node:fs"; import { join, dirname } from "node:path";
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 scripts/postinstall.js
low Package runs install-time scripts (postinstall)MTC-SUP-010
"@egorkurito/apple-mail-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/postinstall.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @egorkurito/apple-mail-mcp
Tools 6
Each tool and what it can reach — statically extracted from the published source.
get_mailboxesingests untrusted inputget_unread_messagesingests untrusted inputget_mail_accountsno sensitive capabilityget_messageno sensitive capabilityget_messagesno sensitive capabilitysearch_mailno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (6 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 92/100 | 3 | 1.13.0 | 2026-09-07 |
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.
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 @egorkurito/apple-mail-mcp --onlineOther implementations of Apple Mail 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
MCP server for Apple Mail - read, search, send, and manage emails via Claude and other AI assistants
Apple Mail MCP server with full-coverage FTS5 body search. Reliable on large mailboxes where AppleScript-based servers timeout.
MCP server giving AI assistants full access to Apple Mail - read, search, compose, organize & analyze emails
More in Communication & Collaboration
One key, 100+ models — chat with any LLM and generate video, images, speech. Free trial at 370.ai.
Retired compatibility stub for the AgentCanary MCP server. Daily briefs continue on X and Telegram.
A Backstage plugin that provides a chat interface for interacting with the MCP Servers.
Signal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.
WhatsApp® reminders and rescheduling for Calendly. Public read-only MCP endpoint.
Open Source Generic MCP Client for testing & evaluating mcp servers and agents