Ext Ops Panel
Open dashboard
Comparison

Nasdaq Data Link vs ECB FX Reference Rates

Nasdaq Data Link is an MCP server published by stefanoamorelli. Marketplaces we read that list it: 1 (Docker MCP Catalog). ECB FX Reference Rates is an MCP server published by pcp183. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 LinkECB FX Reference Rates
Docker MCP Catalog Listed
Version: sha256:c89be15335ac
Forks (GitHub): 16
Pulls (Docker Hub): 15 910
Stars (Docker Hub): 3
Stars (GitHub): 68
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
No figure published
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 ECB FX Reference Rates
FactNasdaq Data LinkECB FX Reference Rates
Marketplaces that list it11
Stars (GitHub) (differs)68No figure on GitHub
Pulls (Docker Hub) (differs)15 910No figure on Docker Hub
Forks (GitHub) (differs)16No figure on GitHub
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/nasdaq-data-link)Remote server (ecb-fx-production.up.railway.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)5Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/stefanoamorelli/nasdaq-data-link-mcpgithub.com/pcp183/ecb-fx
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (4 days 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.

ECB FX Reference Rates

In its own words, on Official MCP Registry:

Official ECB euro reference rates for invoices and tax returns. $0.004/call via x402.

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)

ECB FX Reference Rates As a remote MCP server

Claude Code
claude mcp add --transport http ecb-fx https://ecb-fx-production.up.railway.app/mcp

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

Only ECB FX Reference Rates has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of ECB FX Reference Rates publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of ECB FX Reference Rates publish no settings it asks for, so we do not compare settings.

What it can do: Nasdaq Data Link · What it can do: ECB FX Reference Rates · 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