Ext Ops Panel
Open dashboard
Comparison

Dappier vs GridPulse: U.S. Energy Data

Dappier is an MCP server published by DappierAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). GridPulse: U.S. Energy Data is an MCP server published by noah-silver. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceDappierGridPulse: U.S. Energy Data
Docker MCP Catalog Listed
Version: sha256:ba9b2d17fc77
Forks (GitHub): 16
Pulls (Docker Hub): 17 566
Stars (Docker Hub): 2
Stars (GitHub): 44
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

Dappier vs GridPulse: U.S. Energy Data
FactDappierGridPulse: U.S. Energy Data
Marketplaces that list it11
Stars (GitHub) (differs)44 (better)0 (worse)
Pulls (Docker Hub) (differs)17 566No figure on Docker Hub
Forks (GitHub) (differs)16 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/dappier)On your machine (https://github.com/noah-silver/gridpulse/releases/download/v1.0.1/gridpulse-mcp.mcpb)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/dappierai/dappier-mcpgithub.com/noah-silver/gridpulse
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Dappier

In its own words, on Docker MCP Catalog:

Enable fast, free real-time web search and access premium data from trusted media brands—news, financial markets, sports, entertainment, weather, and more. Build powerful AI agents with Dappier.

GridPulse: U.S. Energy Data

In its own words, on Official MCP Registry:

U.S. grid mix, retail electricity prices and Henry Hub gas prices (EIA), paid per call via x402.

How to run each

Dappier As a local MCP server: Docker image

Claude Code
claude mcp add --env "DAPPIER_API_KEY=<YOUR_DAPPIER_API_KEY>" --transport stdio dappier -- docker run -i --rm -e DAPPIER_API_KEY mcp/dappier

Requires: DAPPIER_API_KEY (secret)

GridPulse: U.S. Energy Data

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: ALGORAND_MNEMONIC (secret), EVM_PRIVATE_KEY (secret)

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

Tools each declares

The marketplaces of GridPulse: U.S. Energy Data publish no list of tools, so we do not compare tools.

Settings each asks for

Only Dappier asks for

  • DAPPIER_API_KEY (secret)

Only GridPulse: U.S. Energy Data asks for

  • ALGORAND_MNEMONIC (secret)
  • EVM_PRIVATE_KEY (secret)

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

What it can do: Dappier · What it can do: GridPulse: U.S. Energy Data · 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