Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/anipotts/imessage-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/anipotts/imessage-mcp/imessage-history)<a href="https://agentmods.dev/mcp/anipotts/imessage-mcp/imessage-history"><img src="https://agentmods.dev/badge/mcp/anipotts/imessage-mcp/imessage-history/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/anipotts/imessage-mcp/imessage-history"><img src="https://agentmods.dev/badge/mcp/anipotts/imessage-mcp/imessage-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
imessage-history scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"imessage-history": {
"command": "npx",
"args": [
"-y",
"[email protected]",
"--contacts",
"none",
"--privacy",
"redacted"
],
"env": {
"IMESSAGE_REFERENCE_KEY_FILE": "${HOME}/.imessage-mcp-reference-key",
"IMESSAGE_DATABASE_ID_FILE": "${HOME}/.imessage-mcp-database-id"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed e8f8656b3200
- 10d ago First seen · 17 lines scan A faf9fcacf09b
imessage-history is an MCP server published in the GitHub repository anipotts/imessage-mcp (24 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
imessage-mcp
MCP server "imessage-mcp" as configured in adelaidasofia/imessage-mcp. Launched with https://github.com/adelaidasofia/imessage-mcp/releases/download/v0.1.0/imessage-.
imessage-connector
MCP server "imessage-connector" as configured in Connected-Mate/imessage-connector. Runs locally from the imessage-connector npm package.
imsg-poke-mcp
MCP server "imsg-poke-mcp" as configured in ish-cs/imessage-poke-bridge. Runs locally from the imsg-poke-mcp Python package.
machina-mcp
MCP server "machina-mcp" as configured in TechNickAI/machina. Runs locally from the machina-mcp npm package.
mirroir
MCP server "mirroir" as configured in jfarcand/mirroir-mcp. Launched with ${workspaceFolder}/.build/release/mirroir-mcp --yolo.
oysterworkflow
MCP server "oysterworkflow" as configured in ShuxinYang111/oysterworkflow. Runs ./mcp/server.mjs with node.