io.github.anipottsbuilds/imessage-mcp
iMessage History
Is the iMessage History MCP server down? Yes. It has given no valid answer since 2026-10-24: install failed.
Read-only MCP server for searching and reading Apple Messages history on macOS.
install failed down since 2026-10-24 · probed 2026-11-15 · unchanged since 2026-10-31
npm error notsup Valid os: darwin npm error notsup Actual os: linux npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-14T08_03_57_
- Run it
- npx -y imessage-mcp@3.3.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/anipottsbuilds/imessage-mcp
- Registry
- active, updated 2026-10-23 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.aneal99/datafordeler-dar-mcp · alive
- io.github.anilloutombam/mcp-failure-lab · crashed on start
- Marey io.github.anilyesilkaya/marey · alive
- iMessage History io.github.anipotts/imessage-mcp · install failed
- io.github.anishmoncivarghese/sonde · crashed on start
- io.github.anivdel/coolftp · alive
- Account Pool io.github.ankitsxchdeva/account-pool-mcp · crashed on start
- NameGender io.github.anpekesen/namegender · alive
Servers that mention imessage.
- LMCP com.local-mcp/local-mcp · needs auth
- MockClip com.mockclip/mockclip · needs auth
- txtreel com.txtreel/txtreel · alive
- io.github.IsaiahDupree/messages-bridge · server error
- autoMessage app.automessage/mcp · not found
- io.github.abryfs/willitsend · alive
- Mock Screenshots io.github.gamercc-apps/mockscreenshots-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-24, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.