# Signal Messaging (via signal-cli) (oci · ghcr.io/joshuawowk/signal-mcp) Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial). - Trust score: 49/100 (low) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - oci · `ghcr.io/joshuawowk/signal-mcp`: 49/100 (this document), [markdown](https://verifymcp.io/servers/joshuawowk-signal-mcp/ghcr-io-joshuawowk-signal-mcp.md), [page](https://verifymcp.io/servers/joshuawowk-signal-mcp/ghcr-io-joshuawowk-signal-mcp) ## Channel facts - Registry: `oci` - Package: `ghcr.io/joshuawowk/signal-mcp` - Version: `1.0.1` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 15 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 76/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 726 tokens (~145/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 53/100 - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the Signal Messaging (via signal-cli) MCP server? Signal Messaging (via signal-cli) runs locally as a container image, launched with docker run --rm -i -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT -e SIGNAL_RPC_URL -e SIGNAL_TCP_HOST -e SIGNAL_TCP_PORT -e SIGNAL_INBOX_PATH -e SIGNAL_POLL_INTERVAL -e SIGNAL_INBOX_RETENTION_DAYS ghcr.io/joshuawowk/signal-mcp:1.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add joshuawowk-signal-mcp -- docker run --rm -i -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT -e SIGNAL_RPC_URL -e SIGNAL_TCP_HOST -e SIGNAL_TCP_PORT -e SIGNAL_INBOX_PATH -e SIGNAL_POLL_INTERVAL -e SIGNAL_INBOX_RETENTION_DAYS ghcr.io/joshuawowk/signal-mcp:1.0.1 ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Cursor ```json { "mcpServers": { "joshuawowk-signal-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "-e", "SIGNAL_RPC_URL", "-e", "SIGNAL_TCP_HOST", "-e", "SIGNAL_TCP_PORT", "-e", "SIGNAL_INBOX_PATH", "-e", "SIGNAL_POLL_INTERVAL", "-e", "SIGNAL_INBOX_RETENTION_DAYS", "ghcr.io/joshuawowk/signal-mcp:1.0.1" ] } } } ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### VS Code ```json { "servers": { "joshuawowk-signal-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "-e", "SIGNAL_RPC_URL", "-e", "SIGNAL_TCP_HOST", "-e", "SIGNAL_TCP_PORT", "-e", "SIGNAL_INBOX_PATH", "-e", "SIGNAL_POLL_INTERVAL", "-e", "SIGNAL_INBOX_RETENTION_DAYS", "ghcr.io/joshuawowk/signal-mcp:1.0.1" ] } } } ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Codex ```bash codex mcp add joshuawowk-signal-mcp -- docker run --rm -i -e SIGNAL_SENDER -e SIGNAL_DEFAULT_RECIPIENT -e SIGNAL_RPC_URL -e SIGNAL_TCP_HOST -e SIGNAL_TCP_PORT -e SIGNAL_INBOX_PATH -e SIGNAL_POLL_INTERVAL -e SIGNAL_INBOX_RETENTION_DAYS ghcr.io/joshuawowk/signal-mcp:1.0.1 ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "joshuawowk-signal-mcp": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "-e", "SIGNAL_RPC_URL", "-e", "SIGNAL_TCP_HOST", "-e", "SIGNAL_TCP_PORT", "-e", "SIGNAL_INBOX_PATH", "-e", "SIGNAL_POLL_INTERVAL", "-e", "SIGNAL_INBOX_RETENTION_DAYS", "ghcr.io/joshuawowk/signal-mcp:1.0.1" ], "enabled": true } } } ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Hermes ```yaml mcp_servers: joshuawowk-signal-mcp: command: "docker" args: ["run", "--rm", "-i", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "-e", "SIGNAL_RPC_URL", "-e", "SIGNAL_TCP_HOST", "-e", "SIGNAL_TCP_PORT", "-e", "SIGNAL_INBOX_PATH", "-e", "SIGNAL_POLL_INTERVAL", "-e", "SIGNAL_INBOX_RETENTION_DAYS", "ghcr.io/joshuawowk/signal-mcp:1.0.1"] ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Netclaw ```json { "McpServers": { "joshuawowk-signal-mcp": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "-e", "SIGNAL_RPC_URL", "-e", "SIGNAL_TCP_HOST", "-e", "SIGNAL_TCP_PORT", "-e", "SIGNAL_INBOX_PATH", "-e", "SIGNAL_POLL_INTERVAL", "-e", "SIGNAL_INBOX_RETENTION_DAYS", "ghcr.io/joshuawowk/signal-mcp:1.0.1" ] } } } ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Other ```json { "mcpServers": { "joshuawowk-signal-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "SIGNAL_SENDER", "-e", "SIGNAL_DEFAULT_RECIPIENT", "-e", "SIGNAL_RPC_URL", "-e", "SIGNAL_TCP_HOST", "-e", "SIGNAL_TCP_PORT", "-e", "SIGNAL_INBOX_PATH", "-e", "SIGNAL_POLL_INTERVAL", "-e", "SIGNAL_INBOX_RETENTION_DAYS", "ghcr.io/joshuawowk/signal-mcp:1.0.1" ] } } } ``` This image reads SIGNAL_SENDER, SIGNAL_DEFAULT_RECIPIENT, SIGNAL_RPC_URL, SIGNAL_TCP_HOST, SIGNAL_TCP_PORT, SIGNAL_INBOX_PATH, SIGNAL_POLL_INTERVAL and SIGNAL_INBOX_RETENTION_DAYS. Set them in your client's env block for this server; docker run -e passes each one through to the container. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 49, +1) No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-03 (score 48, +1) No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-01 (score 47, +1) No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-30 (score 46, +1) No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-27 (score 45, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-25 (score 44, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-23 (score 43, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-21 (score 42, +1) No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (5) ### `signal_send_message` (~127 tokens) Signal Send Message Send a plain Signal DM to the user (or `recipient` if overridden). Use for task-completion pings and FYI updates that don't require a reply. Keep `text` under ~500 chars; include the task name and a one-line result. If the caller has a session_id, pass it so the user can correlate the message back to this conversation. Input parameters: - `recipient`: Optional E.164 number to override the default. - `session_id`: Optional short tag prefixed to the message. - `text` (string, required): The message body. Plain text. ### `signal_send_question` (~215 tokens) Signal Send Question Send a blocking question to the user. Renders as: `QUESTION [session_id]\n\n\n1) opt1\n2) opt2`. The user replies with the number or free text; poll `signal_check_replies` afterwards to read the answer. Use when the agent genuinely cannot proceed without input. Input parameters: - `options`: Optional choices, rendered as a numbered list. Accepts a real list (["A", "B"]) OR a string the client may have serialized: a JSON array '["A","B"]', or newline- or comma-separated text ("A\nB" / "A,… - `question` (string, required): The question text. Be specific; include enough context that the user doesn't need to open Claude to answer. - `recipient`: Optional E.164 override. - `session_id`: Optional short tag for correlating the reply. ### `signal_send_permission_request` (~155 tokens) Signal Send Permission Request Ask the user to approve an action before the agent proceeds. Renders as: `PERMISSION [session_id]\n\n\nContext:\n\n\nReply YES / NO / details.`. Use for irreversible or high-impact operations: deletions, prod changes, spending money, sending external email, anything the user would normally want to confirm. Input parameters: - `action` (string, required): One-line description of what the agent wants to do. - `context` (string, required): Why, scope, and blast radius. Include enough detail that the user can decide without asking follow-ups. - `recipient`: Optional E.164 override. - `session_id`: Optional short tag for correlating the reply. ### `signal_check_replies` (~138 tokens) Signal Check Replies Return recent Signal messages received by the bot account. Reads the inbox.jsonl populated by the subscriber sidecar. Filter by `since` (ISO timestamp), `from_recipient` (E.164), and/or \`session_id` (matches messages whose body contains `[session_id]`). Results are newest-first. Input parameters: - `from_recipient`: Only return messages from this E.164 number. - `limit` (integer): Max messages to return (default 20). - `session_id`: Only return messages whose body contains `[session_id]`. - `since`: Only return messages received at-or-after this ISO ts. ### `signal_health` (~31 tokens) Signal Health Full health check for the signal-mcp server. Call this first if any other tool is misbehaving. ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/joshuawowk-signal-mcp/ghcr-io-joshuawowk-signal-mcp#diagnostics ## Score history - 2026-11-05: 49 - 2026-11-04: 48 - 2026-11-03: 48 - 2026-11-02: 47 - 2026-11-01: 47 - 2026-10-31: 46 - 2026-10-30: 46 - 2026-10-29: 45 - 2026-10-28: 45 - 2026-10-27: 45 - 2026-10-26: 44 - 2026-10-25: 44 - 2026-10-24: 43 - 2026-10-23: 43 - 2026-10-22: 42 - 2026-10-21: 42 - 2026-10-20: 41 ## Common questions ### What is the Signal Messaging (via signal-cli) MCP server? Signal Messaging (via signal-cli) is an MCP server listed in the public MCP registry as io.github.joshuawowk/signal-mcp. Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial). This page covers its container image (ghcr.io/joshuawowk/signal-mcp). ### Is the Signal Messaging (via signal-cli) MCP server safe to use? Signal Messaging (via signal-cli) scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Signal Messaging (via signal-cli) MCP server expose? Signal Messaging (via signal-cli) exposes 5 tools: signal_send_message, signal_send_question, signal_send_permission_request, signal_check_replies, signal_health. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded. ### Is the Signal Messaging (via signal-cli) MCP server still maintained? Signal Messaging (via signal-cli) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the Signal Messaging (via signal-cli) MCP server under? Signal Messaging (via signal-cli) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - GitHub Container Registry: https://ghcr.io/joshuawowk/signal-mcp - Repository: https://github.com/joshuawowk/signal-mcp - Changelog RSS feed: https://verifymcp.io/servers/joshuawowk-signal-mcp/ghcr-io-joshuawowk-signal-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/joshuawowk-signal-mcp/ghcr-io-joshuawowk-signal-mcp.json - HTML version of this page: https://verifymcp.io/servers/joshuawowk-signal-mcp/ghcr-io-joshuawowk-signal-mcp