Ext Ops Panel
Open dashboard
Comparison

WolframAlpha vs io.github.cyanheads/nasa-power-mcp-server

WolframAlpha is an MCP server published by SecretiveShell. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.cyanheads/nasa-power-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceWolframAlphaio.github.cyanheads/nasa-power-mcp-server
Docker MCP Catalog Listed
Version: sha256:4cd89d002d55
Forks (GitHub): 21
Pulls (Docker Hub): 47 829
Stars (Docker Hub): 6
Stars (GitHub): 75
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 1
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 io.github.cyanheads/nasa-power-mcp-server
FactWolframAlphaio.github.cyanheads/nasa-power-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)75 (better)1 (worse)
Pulls (Docker Hub) (differs)47 829No figure on Docker Hub
Forks (GitHub) (differs)21 (better)0 (worse)
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (mcp/wolfram-alpha)On your machine (@cyanheads/nasa-power-mcp-server)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 112, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/secretiveshell/mcp-wolfram-alphagithub.com/cyanheads/nasa-power-mcp-server
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-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

WolframAlpha

In its own words, on Docker MCP Catalog:

Connect your chat repl to wolfram alpha computational intelligence.

io.github.cyanheads/nasa-power-mcp-server

In its own words, on Official MCP Registry:

Query NASA POWER solar, wind, building, and agroclimatology data.

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)

io.github.cyanheads/nasa-power-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio nasa-power-mcp-server -- npx -y @cyanheads/nasa-power-mcp-server

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of io.github.cyanheads/nasa-power-mcp-server publish no list of tools, so we do not compare tools.

Settings each asks for

Only WolframAlpha asks for

  • WOLFRAM_API_KEY (secret)

Only io.github.cyanheads/nasa-power-mcp-server asks for

  • CANVAS_ABSOLUTE_CAP_MS
  • CANVAS_DEFAULT_MEMORY_LIMIT_MB
  • CANVAS_MAX_CANVASES_PER_TENANT
  • CANVAS_PROVIDER_TYPE
  • CANVAS_TTL_MS
  • MCP_AUTH_MODE
  • MCP_HTTP_ENDPOINT_PATH
  • MCP_HTTP_HOST
  • MCP_HTTP_PORT
  • MCP_LOG_LEVEL
  • MCP_TRANSPORT_TYPE
  • NASA_POWER_DATAFRAME_DROP_ENABLED

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: WolframAlpha · What it can do: io.github.cyanheads/nasa-power-mcp-server · 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. 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