io.github.parasxos/apple-mail-mcp
PYPI · APPLE-MAILBOX-MCP
Fast local Apple Mail MCP: indexed search, full-text bodies, verified sends, triage. macOS.
Available components
Last scanned (22 hours ago)
Scores higher than 94% of PyPI servers
Category Communication
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to parasxos/apple-mail-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1984 tokens (~94/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 −8
- Stability: pass → 0.40 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 19 Oct 26 −1
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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
- Package version: 1.8.0 → 1.8.3 functional
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 4 Nov 2026 · Analysed pypi/apple-mailbox-mcp@1.8.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | parasxos/apple-mail-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/parasxos/apple-mail-mcp/.github/workflows/release.yml@refs/tags/v1.8.3 |
| Rekor log index | 3315945526 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d6f2cbc8557e11ebe16810bb46a61f80c5afa07a53b27c1ef2d694be1ebaf9d6 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit Read the activity history ~126
Read the local mutation ledger with time, tool, event, plan, and operation filters.
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | – | Only return activity with this event name. |
| limit | integer | – | Maximum number of results to return. |
| operation_id | – | – | Operation ID that joins related activity across processes. |
| plan_id | – | – | Triage plan ID returned by a planning tool. |
| since | – | – | Inclusive ISO-8601 start bound; calendar prefixes are accepted. |
| tool | – | – | Only return activity emitted by this tool name. |
| until | – | – | Inclusive ISO-8601 end bound; calendar prefixes are accepted. |
Structured output declared, but exposes no named fields.
No examples provided.
cancel_scheduled Cancel a scheduled email ~39
Revoke a pending scheduled email locally and, when needed, in Exchange.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Scheduled-email ID returned when it was created. |
Structured output declared, but exposes no named fields.
No examples provided.
create_draft Create an email draft ~122
Create a never-sent draft in the selected identity's server-side Drafts folder.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Plain-text email content; paragraph breaks are preserved. |
| cc | – | – | Optional comma-separated Cc recipients. |
| from_identity | – | – | Configured sending identity; omit it to use the default. |
| in_reply_to | string | – | Optional Message-ID of the message being answered, so the mail threads as a reply. |
| subject | string | yes | Email subject line. |
| to | string | yes | Comma-separated primary recipients, including optional display names. |
Structured output declared, but exposes no named fields.
No examples provided.
doctor Check email setup ~21
Diagnose permissions, identities, transports, scheduling, storage, and indexing.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_attachment Save an attachment for reading ~49
Save one attachment to the configured temporary directory for reading.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | Attachment part ID returned by get_email. |
| id | string | yes | Envelope ID of the email containing the attachment. |
Structured output declared, but exposes no named fields.
No examples provided.
get_email Read an email ~59
Read one email by envelope ID at full, metadata, or minimal detail.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Envelope ID returned by search, recent, or thread tools. |
| view | string | – | Payload size: full, metadata without bodies, or minimal. |
Structured output declared, but exposes no named fields.
No examples provided.
get_emails_batch Read multiple emails ~62
Read up to 50 emails in one bounded request, with per-ID errors.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Envelope IDs returned by search, recent, or thread tools. |
| view | string | – | Payload size: full, metadata without bodies, or minimal. |
Structured output declared, but exposes no named fields.
No examples provided.
get_thread Read an email thread ~33
Return the messages in one conversation in chronological order.
| Name | Type | Req | Description |
|---|---|---|---|
| thread_id | string | yes | Conversation ID returned on an email reference. |
Structured output declared, but exposes no named fields.
No examples provided.
list_mailboxes List mailboxes ~20
List configured mailboxes with server and locally readable counts.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_recent List recent emails ~65
List recent messages, optionally scoped to an account and mailbox.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Account UUID; omit it to include every configured account. |
| limit | integer | – | Maximum number of results to return. |
| mailbox | – | – | Mailbox name to search, such as INBOX or Archive. |
Structured output declared, but exposes no named fields.
No examples provided.
list_scheduled List scheduled emails ~50
List healthy and damaged scheduled-mail records by lifecycle state.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return. |
| state | – | – | Scheduled-mail state to return; omit it to include all states. |
Structured output declared, but exposes no named fields.
No examples provided.
mailbox_create Create a mailbox ~54
Create a mailbox idempotently and report live and index verification.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account UUID that will own the mailbox. |
| path | string | yes | Mailbox path within the account; slashes create nested folders. |
Structured output declared, but exposes no named fields.
No examples provided.
mailbox_delete Delete a mailbox ~53
Delete an empty mailbox only, with live verification and safe fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account UUID that owns the mailbox. |
| path | string | yes | Mailbox path within the account; slashes create nested folders. |
Structured output declared, but exposes no named fields.
No examples provided.
refresh_mail Refresh mail ~56
Ask Mail.app to fetch new mail and report the before/after snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_seconds | number | – | Maximum seconds allowed for the Mail.app refresh request. |
| wait_seconds | number | – | Seconds to wait after Mail.app starts refreshing. |
Structured output declared, but exposes no named fields.
No examples provided.
reply_email Reply to an email ~144
Reply with correct threading, optional history, attachments, and reply-all.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | – | – | Optional list of local file paths, one path per item. |
| bcc | – | – | Optional comma-separated Bcc recipients. |
| body | string | yes | Plain-text email content; paragraph breaks are preserved. |
| cc | – | – | Optional comma-separated Cc recipients. |
| from_identity | – | – | Configured sending identity; omit it to use the default. |
| id | string | yes | Envelope ID of the email being answered. |
| include_history | boolean | – | Quote the original message below the new reply. |
| reply_all | boolean | – | Also copy the original To and Cc recipients, excluding yourself. |
Structured output declared, but exposes no named fields.
No examples provided.
schedule_email Schedule an email ~191
Freeze an email now and schedule local or Exchange-side delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | – | – | Optional list of local file paths, one path per item. |
| bcc | – | – | Optional comma-separated Bcc recipients. |
| body | string | yes | Plain-text email content; paragraph breaks are preserved. |
| cc | – | – | Optional comma-separated Cc recipients. |
| from_identity | – | – | Configured sending identity; omit it to use the default. |
| in_reply_to | string | – | Optional Message-ID of the message being answered, so the mail threads as a reply. |
| references | string | – | Optional References header of the message being answered; in_reply_to is appended to it. |
| send_at | string | yes | Delivery time in ISO-8601; a timestamp without an offset is local time. |
| subject | string | yes | Email subject line. |
| to | string | yes | Comma-separated primary recipients, including optional display names. |
Structured output declared, but exposes no named fields.
No examples provided.
search_emails Search emails ~223
Search local envelope data and indexed body content. Check the returned FTS coverage before treating no matches as proof that no email exists. Sender filters are case-insensitive substring matches.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Account UUID; omit it to include every configured account. |
| after | – | – | Only include mail after this ISO-8601 date or timestamp. |
| before | – | – | Only include mail before this ISO-8601 date or timestamp. |
| from_addr | – | – | Sender name, address, or address fragment to match. |
| has_attachment | – | – | True for mail with attachments, false for mail without them. |
| limit | integer | – | Maximum number of results to return. |
| mailbox | – | – | Mailbox name to search, such as INBOX or Archive. |
| offset | integer | – | Number of matching results to skip for pagination. |
| query | string | – | Words to find in the subject, sender, snippet, or indexed body. |
| to_addr | – | – | Recipient name, address, or address fragment to match. |
| unread_only | boolean | – | When true, include only unread messages. |
Structured output declared, but exposes no named fields.
No examples provided.
send_email Send an email ~120
Compose standards-correct MIME and send it through the selected identity.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | – | – | Optional list of local file paths, one path per item. |
| bcc | – | – | Optional comma-separated Bcc recipients. |
| body | string | yes | Plain-text email content; paragraph breaks are preserved. |
| cc | – | – | Optional comma-separated Cc recipients. |
| from_identity | – | – | Configured sending identity; omit it to use the default. |
| subject | string | yes | Email subject line. |
| to | string | yes | Comma-separated primary recipients, including optional display names. |
Structured output declared, but exposes no named fields.
No examples provided.
triage_apply Apply reviewed mailbox changes ~88
Apply one reviewed plan, optionally excluding selected envelope IDs, and verify the retained messages. A successful claim consumes the whole plan once.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_ids | – | – | Envelope IDs from this reviewed plan to leave untouched. Omit or pass an empty list to apply the full plan. At least one message must remain selected. |
| plan_id | string | yes | Triage plan ID returned by a planning tool. |
Structured output declared, but exposes no named fields.
No examples provided.
triage_plan Prepare mailbox changes ~211
Prepare a reviewable bulk-change plan; sender filters use case-insensitive substring matching.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Account UUID; omit it to include every configured account. |
| actions | – | – | Mailbox actions to stage for every selected message. |
| after | – | – | Only include mail after this ISO-8601 date or timestamp. |
| before | – | – | Only include mail before this ISO-8601 date or timestamp. |
| from_addr | – | – | Sender name, address, or address fragment to match. |
| has_attachment | – | – | True for mail with attachments, false for mail without them. |
| limit | integer | – | Maximum messages to stage; 0 uses the configured safe plan cap. |
| mailbox | – | – | Mailbox name to search, such as INBOX or Archive. |
| query | string | – | Words to find in the subject, sender, snippet, or indexed body. |
| to_addr | – | – | Recipient name, address, or address fragment to match. |
| unread_only | boolean | – | When true, include only unread messages. |
Structured output declared, but exposes no named fields.
No examples provided.
triage_plan_delete Prepare email deletion ~198
Prepare a capped Trash plan whose sender filter is exact, never a broad substring match.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Account UUID; omit it to include every configured account. |
| after | – | – | Only include mail after this ISO-8601 date or timestamp. |
| before | – | – | Only include mail before this ISO-8601 date or timestamp. |
| from_addr | – | – | Exact sender email address to match; fragments never select mail. |
| has_attachment | – | – | True for mail with attachments, false for mail without them. |
| limit | integer | – | Maximum messages to stage; 0 uses the configured deletion cap. |
| mailbox | – | – | Mailbox name to search, such as INBOX or Archive. |
| query | string | – | Words to find in the subject, sender, snippet, or indexed body. |
| to_addr | – | – | Recipient name, address, or address fragment to match. |
| unread_only | boolean | – | When true, include only unread messages. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.parasxos/apple-mail-mcp server?
io.github.parasxos/apple-mail-mcp runs locally as a PyPI package, launched with uvx apple-mailbox-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · apple-mailbox-mcp
claude mcp add parasxos-apple-mail-mcp -- uvx apple-mailbox-mcp
What is the io.github.parasxos/apple-mail-mcp server?
io.github.parasxos/apple-mail-mcp is listed in the public MCP registry as io.github.parasxos/apple-mail-mcp. Fast local Apple Mail MCP: indexed search, full-text bodies, verified sends, triage. macOS. This page covers its PyPI package (apple-mailbox-mcp).
Is the io.github.parasxos/apple-mail-mcp server safe to use?
io.github.parasxos/apple-mail-mcp scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.parasxos/apple-mail-mcp server expose?
io.github.parasxos/apple-mail-mcp exposes 21 tools: search_emails, get_email, get_emails_batch, get_thread, list_mailboxes, and 16 more. Their descriptions and schemas cost roughly 1,984 tokens of context every time the server is loaded.
Is the io.github.parasxos/apple-mail-mcp server still maintained?
io.github.parasxos/apple-mail-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.parasxos/apple-mail-mcp server under?
io.github.parasxos/apple-mail-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.