LetKite (dev) vs Signal Desk paid tools
LetKite (dev) is an MCP server published by letkite.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  LetKite (dev) |  Signal Desk paid tools |
|---|---|---|
| Official MCP Registry | Listed, marked deprecated Version: 1.7.0-rc.2 No figure published Not marked · First seen |
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 | LetKite (dev) | Signal Desk paid tools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-24 (worse) | 2026-10-31 (better) |
| Where it runs (differs) | Remote server (mcp.dev.letkite.com/mcp) | Remote server (x402-mcp.huntercarver24.workers.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/huntercarver24/signal-desk |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-19 | 2026-10-28 |
| Endpoint at the last check (differs) | Status out of date: last check 30 h ago returned HTTP 401 | 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
LetKite (dev)
Run commands and manage files on your own machines. Needs a LetKite account; OAuth sign-in.
Signal Desk paid tools
x402-paid tools: render pages, host files, delayed callbacks, pump.fun launch feed, trend radar
How to run each
LetKite (dev) As a remote MCP server
claude mcp add --transport http letkite-dev https://mcp.dev.letkite.com/mcpSignal 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.
Both endpoints responded at the last daily 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: LetKite (dev) · What it can do: Signal Desk paid tools · Compare two other plugins
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.