Ext Ops Panel
Open dashboard
Comparison

Nasdaq Data Link vs Dados B3

Nasdaq Data Link is an MCP server published by stefanoamorelli. Marketplaces we read that list it: 1 (Docker MCP Catalog). Dados B3 is an MCP server published by Val7h. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceNasdaq Data LinkDados B3
Docker MCP Catalog Listed
Version: sha256:c89be15335ac
Forks (GitHub): 15
Pulls (Docker Hub): 15 667
Stars (Docker Hub): 3
Stars (GitHub): 67
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.9.0
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

Nasdaq Data Link vs Dados B3
FactNasdaq Data LinkDados B3
Marketplaces that list it11
Stars (GitHub) (differs)67 (better)0 (worse)
Pulls (Docker Hub) (differs)15 667No figure on Docker Hub
Forks (GitHub) (differs)15 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/nasdaq-data-link)Remote server (dadosb3.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)5Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/stefanoamorelli/nasdaq-data-link-mcpgithub.com/val7h/dados-b3-mcp
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 27 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

Nasdaq Data Link

In its own words, on Docker MCP Catalog:

MCP server to interact with the data feeds provided by the Nasdaq Data Link. Developed by the community and maintained by Stefano Amorelli.

Dados B3

In its own words, on Official MCP Registry:

Brazilian stock (B3) fundamentals: ratios, dividends, scores, FIIs, ETFs, BDRs. Open methodology.

How to run each

Nasdaq Data Link As a local MCP server: Docker image

Claude Code
claude mcp add --env "NASDAQ_DATA_LINK_API_KEY=<YOUR_NASDAQ_DATA_LINK_API_KEY>" --transport stdio nasdaq-data-link -- docker run -i --rm -e NASDAQ_DATA_LINK_API_KEY mcp/nasdaq-data-link

Requires: NASDAQ_DATA_LINK_API_KEY (secret)

Dados B3 As a remote MCP server

Claude Code
claude mcp add --transport http dados-b3 https://dadosb3.com/mcp/

Requires: DADOS_B3_API_KEY (secret)

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

Only Dados B3 has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Only Nasdaq Data Link asks for

  • NASDAQ_DATA_LINK_API_KEY (secret)

Only Dados B3 asks for

  • DADOS_B3_API_KEY (secret)

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

What it can do: Nasdaq Data Link · What it can do: Dados B3 · 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