snodo-mcp vs Signal Desk paid tools
snodo-mcp is an MCP server published by snodo-dev. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Signal Desk paid tools is an MCP server published by huntercarver24. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  snodo-mcp |  Signal Desk paid tools |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.28.3 Downloads/month (PyPI): 2 587 Downloads/week (PyPI): 323 Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.2 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 | snodo-mcp | Signal Desk paid tools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | 2026-11-05 (better) | 2026-10-31 (worse) |
| Where it runs (differs) | On your machine (snodo-mcp) | Remote server (x402-mcp.huntercarver24.workers.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/snodo-dev/snodo | github.com/huntercarver24/signal-desk |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-28 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 h ago |
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
snodo-mcp
Snodo MCP — MCP servers, planning, recon, and jobs
Signal Desk paid tools
x402-paid tools: render pages, host files, delayed callbacks, pump.fun launch feed, trend radar
How to run each
snodo-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Signal Desk paid tools As a remote MCP server
claude mcp add --transport http signal-desk https://x402-mcp.huntercarver24.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Signal Desk paid tools has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: snodo-mcp · What it can do: Signal Desk paid tools · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.