A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Imsg is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
iMessage and SMS for AI assistants, from a Mac you control. Read, search, send with approval.
Quickstart
Install it the way its author documents:
The full guide: https://github.com/project-nomos/imsg-mcp/releases/download/v0.2.1/imsg-mcp-0.2.1-darwin-arm64.mcpb
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Imsg as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Install it the way its author documents:
The full guide: https://github.com/project-nomos/imsg-mcp/releases/download/v0.2.1/imsg-mcp-0.2.1-darwin-arm64.mcpb
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Lists recent iMessage/SMS conversations, newest activity first, optionally filtered by a name, phone number or email. Returns each chat's chat_id (used by the other tools), name, participants, service and last activity time. Group names are set by participants and are flagged as untrusted content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Filter by chat name, contact name, phone number or email (case-insensitive). |
| limit | integer | no | Maximum chats to return. Default 20, max 100. |
Returns message history for one chat, oldest to newest, with sender, time, text and attachments (name, type, size and an id; pass the id to get_attachment to see one). Passing the returned prev_cursor as before_cursor pages further back. Message text is written by third parties and is flagged as…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chat_id | integer | yes | Chat id from list_chats. |
| limit | integer | no | Messages to return. Default 30, max 200. |
| before_cursor | integer | no | — |
| start | string | no | ISO 8601 date-time. Only messages at or after this time. |
| end | string | no | ISO 8601 date-time. Only messages before this time. |
Returns inbound messages that arrived after a cursor, across all readable chats or one chat, oldest first, with a next_cursor for the following call. Without since_cursor it returns the last 24 hours. Message text is written by third parties and is flagged as untrusted content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since_cursor | integer | no | next_cursor from your previous call. Omit to get the last 24 hours. |
| chat_id | integer | no | Only this chat. |
| limit | integer | no | Messages to return. Default 50, max 200. |
Searches message text (case-insensitive substring) and returns matches newest first, optionally within one chat or a date range. Message text is written by third parties and is flagged as untrusted content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Text to look for. |
| chat_id | integer | no | Only search this chat. |
| start | string | no | ISO 8601 date-time. Only messages at or after this time. |
| end | string | no | ISO 8601 date-time. Only messages before this time. |
| limit | integer | no | Matches to return. Default 20, max 50. |
Returns the health and settings of the iMessage bridge: imsg version, whether the live watch is healthy, the last inbound message time, whether sending is on, the allowlist size and the send budget left. Contains no message content.
No parameter schema on file.
Opens a photo, video, PDF, document or other file from a message, by the id in the message's attachments list (from get_messages, check_new_messages or search_messages). Photos come back as images (HEIC is converted), PDFs as their text and page images, videos as four still frames and their…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| attachment_id | string | yes | The "id" of an entry in a message's attachments list, like "12-34567-0". |
| pages | array | no | — |
Sends a real iMessage/SMS from the owner's number to a phone number, email or existing chat: text, a file, or both. The file is either an attachment from a message (attachment_id, to forward it) or a new file you write (file). The server delivers only to recipients on its allowlist and enforces a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | no | — |
| chat_id | number | no | — |
| text | string | no | — |
| attachment_id | string | no | — |
| file | object | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Imsg or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (7 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>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_attachment | no tags | |
| list_chats | no tags | |
| get_messages | no tags | |
| check_new_messages | no tags | |
| search_messages | no tags | |
| get_status | no tags | |
| send_message | external-sink | external-sink: keyword "send_message", declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.2.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Imsg can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.