Imessage (anipotts) MCP Server
imessage-mcp
npm
v1.3.1
Source verified
Published by anipotts — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
iMessage MCP server — 25 tools for searching, analyzing, and exploring your entire iMessage history on macOS
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. 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 |
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 1
high Shell/command execution in server code (dist/contacts.js)MTC-SRC-002
In the server's implementation (`dist/contacts.js:6`): 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: ecFileSync } from "node:child_process"; import { existsSync } from "node:fs"; import { dirname, resolve } from "node:pat
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/contacts.js
Tools 25
Each tool and what it can reach — statically extracted from the published source.
contact_statsno sensitive capabilityconversation_gapsno sensitive capabilitydouble_textsno sensitive capabilityfirst_last_messageno sensitive capabilityforgotten_contactsno sensitive capabilityget_contactno sensitive capabilityget_conversationno sensitive capabilityget_edited_messagesno sensitive capabilityget_group_chatno sensitive capabilityget_message_effectsno sensitive capability
Show 15 more tools ↓
get_reactionsno sensitive capabilityget_read_receiptsno sensitive capabilityget_threadno sensitive capabilityhelpno sensitive capabilitylist_attachmentsno sensitive capabilitylist_contactsno sensitive capabilitylist_group_chatsno sensitive capabilitymessage_statsno sensitive capabilityon_this_dayno sensitive capabilityresolve_contactno sensitive capabilitysearch_messagesno sensitive capabilitystreaksno sensitive capabilitytemporal_heatmapno sensitive capabilitywho_initiatesno sensitive capabilityyearly_wrappedno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (25 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 2
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.3.1 latest |
A 94/100 | 1 | 1.13.0 | 2026-09-07 |
v1.3.0 |
A 93/100 | 1 | 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.
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 imessage-mcp --onlineOther implementations of Imessage 5
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
MCP server for iMessage
MCP server for iMessage
MCP server for reading and sending iMessages on macOS
An MCP server exposing your local iMessage history (macOS, read-only).
MCP server and AI bridge for iMessage on macOS
More in Analytics & Monitoring
Public-safe MCP admin discovery contract descriptors and response builders.
Pokemon Champions battle advisor MCP server
Airflow MCP server — DAG list, runs, task instances, log tails, trigger and clear over the Airflow REST API
MCP analytics wrapper SDK that instruments MCP tool declarations with telemetry.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
AI-native social listening. Monitor buying signals and run GTM workflows via natural language.