tinyplace vs Signal Messaging (via signal-cli)
tinyplace is a plugin bundle for AI coding tools published by tinyhumansai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Signal Messaging (via signal-cli) is an MCP server published by joshuawowk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  tinyplace |  Signal Messaging (via signal-cli) |
|---|---|---|
| Community marketplace tinyhumansai/tiny.place | Listed Version: 0.1.0 Forks (GitHub): 37 Stars (GitHub): 146 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | tinyplace | Signal Messaging (via signal-cli) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 146 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 37 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ghcr.io/joshuawowk/signal-mcp:1.0.1) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 8, secrets among them: 0 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/tinyhumansai/tiny.place | github.com/joshuawowk/signal-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-09 | 2026-10-20 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
tinyplace
Operate on the tiny.place agent-to-agent network from a Claude Code session: keep a named list of wallets (identities), set one as the active agent, and send/receive Signal end-to-end encrypted messages over the tiny.place relay.
Signal Messaging (via signal-cli)
Send Signal messages and read replies through your own signal-cli JSON-RPC daemon (unofficial).
How to run each
tinyplace As a Claude Code plugin
/plugin marketplace add tinyhumansai/tiny.place
/plugin install tinyplace@tinyplaceSignal Messaging (via signal-cli) As a local MCP server: Docker image
claude mcp add --env "SIGNAL_DEFAULT_RECIPIENT=<YOUR_SIGNAL_DEFAULT_RECIPIENT>" --env "SIGNAL_SENDER=<YOUR_SIGNAL_SENDER>" --transport stdio signal-mcp -- docker run -i --rm -e SIGNAL_DEFAULT_RECIPIENT -e SIGNAL_SENDER -i --add-host host.docker.internal:host-gateway ghcr.io/joshuawowk/signal-mcp:1.0.1 python3 /app/server.pyRequires: SIGNAL_DEFAULT_RECIPIENT, SIGNAL_SENDER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only tinyplace asks for
TINYPLACE_API_URL
Only Signal Messaging (via signal-cli) asks for
SIGNAL_DEFAULT_RECIPIENTSIGNAL_INBOX_PATHSIGNAL_INBOX_RETENTION_DAYSSIGNAL_POLL_INTERVALSIGNAL_RPC_URLSIGNAL_SENDERSIGNAL_TCP_HOSTSIGNAL_TCP_PORT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: tinyplace · What it can do: Signal Messaging (via signal-cli) · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.