apple-mail-mcp (parasxos/apple-mail-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 21 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

apple-mail-mcp

MCP server for Apple Mail: sub-ms search over 300k+ messages via Mail's own SQLite index, verified sends, Exchange body backfill, triage plan/review/apply. 849 tests, MIT.

→ parasxos/apple-mail-mcp· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

parasxos

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configEMAIL_MCP_MAIL_DIR
configEMAIL_MCP_SOURCE
configEMAIL_MCP_READ_ONLY👓 Read-only mail mode. Set =1 and only the 11
configEMAIL_MCP_MAX_BODY_BYTES
configEMAIL_MCP_ATTACH_DIR
configEMAIL_MCP_FROM_ADDR
configEMAIL_MCP_FROM_NAME
configEMAIL_MCP_SEND_ALLOW_ALL
configEMAIL_MCP_SEND_ALLOWLIST
configEMAIL_MCP_BCC_SELF
configEMAIL_MCP_SEND_HOST
configEMAIL_MCP_SEND_USER
configEMAIL_MCP_DELIVERY_CMD
configEMAIL_MCP_SEND_RETRIES
configEMAIL_MCP_TRIAGE_MAX
configEMAIL_MCP_TRIAGE_DELETE_MAX
configEMAIL_MCP_TRIAGE_TTL
configEMAIL_MCP_TRIAGE_TIMEOUT
configEMAIL_MCP_TRIAGE_VERIFY_POLLS
configEMAIL_MCP_TRIAGE_VERIFY_INTERVAL
configEMAIL_MCP_FTS_ENABLED
configEMAIL_MCP_FTS_MAX_HITS
configEMAIL_MCP_FTS_INLINE_BATCH
configEMAIL_MCP_FTS_INLINE_BUDGET
configEMAIL_MCP_FTS_DOC_CAP
configEMAIL_MCP_FTS_RECONCILE_DAYS
configEMAIL_MCP_MAX_ATTACH_MB
configEMAIL_MCP_LOG_FILE
configEMAIL_MCP_LOG_LEVEL
configEMAIL_MCP_SSH_BOOTSTRAP
configEMAIL_MCP_IDENTITIES
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

21/21 tools missing one or more hints — tool_search_emails (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); tool_get_email (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); tool_get_emails_batch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/parasxos/apple-mail-mcp)](https://m8ven.ai/mcp/parasxos/apple-mail-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2bca3126473ffa48c73a21e54dbdc83b7fa357a1
code hash: a0c6577d718ce77e5cf15dbebc42f88e9d9038c90a78aac09e4e5c269890c719
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client