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/ish-cs/imessage-poke-bridgeWrote 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/ish-cs/imessage-poke-bridge/imsg-poke-mcp)<a href="https://agentmods.dev/mcp/ish-cs/imessage-poke-bridge/imsg-poke-mcp"><img src="https://agentmods.dev/badge/mcp/ish-cs/imessage-poke-bridge/imsg-poke-mcp/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/ish-cs/imessage-poke-bridge/imsg-poke-mcp"><img src="https://agentmods.dev/badge/mcp/ish-cs/imessage-poke-bridge/imsg-poke-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
imsg-poke-mcp 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 11d ago.
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
{ "imsg-poke-mcp": { "command": "uvx", "args": [ "imsg-poke-mcp" ] } }
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.
- 11d ago First seen · 8 lines scan A 22bddda3bfef
imsg-poke-mcp is an MCP server published in the GitHub repository ish-cs/imessage-poke-bridge (1 stars, last pushed 2mo ago), 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-31.
Other mcp servers, from other repositories
che-ical-mcp
MCP server "che-ical-mcp" as configured in PsychQuant/che-ical-mcp. Launched with https://github.com/PsychQuant/che-ical-mcp/releases/download/v1.14.1/che-ical-mc.
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.
hunch
Drive your Mac focus-free over MCP: OS APIs, AppleScript, CDP, and Accessibility. Runs locally from the hunch-sdk Python package.
plonk
MCP server for Plonk, a macOS window manager: zones you draw yourself, workspaces, keep-awake, screenshots and on-device OCR, as tools an agent can call. Runs locally from the plonk-mcp npm package.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.