Needle Remote vs PokerData
Needle Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). PokerData is an MCP server published by hft-studio. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 |  Needle Remote |   PokerData |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.4 Downloads/month (npm): 995 Downloads/week (npm): 838 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.4 Downloads/month (npm): 995 Downloads/week (npm): 838 Forks (GitHub): 0 Stars (GitHub): 2 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 | Needle Remote | PokerData |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Remote server (mcp.needle.app/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/hft-studio/pokerdata-mcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 301 | Responded 10 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
Needle Remote
Production-ready RAG service to search and retrieve data from your documents.
PokerData
GTO poker solver data: NLHE/PLO preflop ranges, postflop strategy, EV. 6-max NL preflop free.
How to run each
Needle Remote As a remote MCP server
claude mcp add --transport http needle https://mcp.needle.app/mcpRequires: NEEDLE_API_KEY (secret)
PokerData As a remote MCP server
claude mcp add --transport http pokerdata https://pokerdata.io/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: POKERDATA_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of PokerData 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
Only Needle Remote asks for
NEEDLE_API_KEY (secret)
Only PokerData asks for
POKERDATA_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Needle Remote · What it can do: PokerData · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.