Ext Ops Panel
Open dashboard
Comparison

WolframAlpha vs PokerData

WolframAlpha is an MCP server published by SecretiveShell. 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

Where each is published
MarketplaceWolframAlphaPokerData
Docker MCP Catalog Not seen in the last pass
Version: sha256:4cd89d002d55
Forks (GitHub): 20
Pulls (Docker Hub): 48 211
Stars (Docker Hub): 6
Stars (GitHub): 76
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

WolframAlpha vs PokerData
FactWolframAlphaPokerData
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)76 (better)2 (worse)
Pulls (Docker Hub) (differs)48 211No figure on Docker Hub
Forks (GitHub) (differs)20 (better)0 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/wolfram-alpha)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/secretiveshell/mcp-wolfram-alphagithub.com/hft-studio/pokerdata-mcp
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)no remote endpoint we checkResponded 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

WolframAlpha

In its own words, on Docker MCP Catalog:

Connect your chat repl to wolfram alpha computational intelligence.

PokerData

In its own words, on Official MCP Registry:

GTO poker solver data: NLHE/PLO preflop ranges, postflop strategy, EV. 6-max NL preflop free.

How to run each

WolframAlpha As a local MCP server: Docker image

Claude Code
claude mcp add --env "WOLFRAM_API_KEY=<YOUR_WOLFRAM_API_KEY>" --transport stdio wolfram-alpha -- docker run -i --rm -e WOLFRAM_API_KEY mcp/wolfram-alpha

Requires: WOLFRAM_API_KEY (secret)

PokerData As a remote MCP server

Claude Code
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 PokerData has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of PokerData publish no list of tools, so we do not compare tools.

Settings each asks for

Only WolframAlpha asks for

  • WOLFRAM_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: WolframAlpha · 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.

Where the data comes from: how the catalog is built