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.
npx agentmods add mcp/bowlofarugula/texting/imessagegit clone --depth 1 https://github.com/bowlofarugula/textingGrade A, and why
imessage 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- whatsapp — 89% identical, 2 lines differ
What it actually says
{
"imessage": {
"command": "/bin/sh",
"args": [
"-c",
"BUN=\"$(command -v bun || echo \"$HOME/.bun/bin/bun\")\"; exec \"$BUN\" run --cwd \"${CLAUDE_PLUGIN_ROOT}\" --shell=bun --silent start"
]
}
}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.
- yesterday First seen · 9 lines scan A 8c9ca873537f
imessage is an MCP server published in the GitHub repository bowlofarugula/texting (1 stars, last pushed 2mo ago), licensed Apache-2.0. 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-31.
Other mcp servers, from other repositories
imessage-history
iMessage MCP server — 25 tools for searching, analyzing, and exploring your entire iMessage history on macOS. Runs locally from the imessage-mcp npm package. Needs 2 environment variables to run.
imessage-mcp
Read-only MCP for iMessage, SMS, MMS, and RCS history already present in Apple Messages on Mac. Runs locally from the imessage-mcp npm package. Needs 6 environment variables to run.
imessage
MCP server "imessage" as configured in adelaidasofia/imessage-mcp. Launched with uv --directory ${CLAUDE_PLUGIN_ROOT} run main.py.
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.