Nasdaq Data Link (community)

Stefano Amorelli (OSS) · Market & Financial Data

MCP ServerCommunity

Community-maintained MCP server for Nasdaq Data Link (formerly Quandl), built on Nasdaq's official Python SDK. Five generic tools search, inspect, retrieve and export any dataset a key can reach, including World Bank indicators, Equities 360 fundamentals, Nasdaq retail trading activity (RTAT) and Nasdaq Fund Network mutual fund and ETF data on fees, performance and flows.

market dataeconomic indicatorscompany fundamentalsfund datadataset exportscommunity maintained

Status

Community

Auth

API key

Hosting

Local

Community rating

Not rated yet

Role

Source

Provides data. A read-only feed from one provider; it answers questions, doesn't act, and doesn't expect other servers alongside it. More on Source servers → All seven roles →

Open documentation →

Caveats

Community-reported coverage includes World Bank, Equities 360, retail trading activity and Nasdaq Fund Network datasets; compatibility and example dataset availability have not been independently verified.
The documented tools retrieve and export data. No source-data modification, account management or order-placement tools are documented.
Community-documented setup runs locally, stores the API key in an environment file and fetches data from Nasdaq Data Link. Its architecture also includes an MCP client and LLM, so local hosting does not establish that retrieved data stays on the machine.
An API key is required. The submission limits dataset access to what that key can reach; the source does not establish subscription entitlements or data redistribution rights.
Community-documented installation requires Python 3.13+, the MCP CLI and manual environment configuration; no hosted MCP endpoint is provided.
The repository lists an MIT license and explicitly states that the project is neither affiliated with nor endorsed by Nasdaq.
Start with read-only scopes and keep client-side approval prompts on until the connection is proven.

Rate this server

How to connect Nasdaq Data Link (community)

Step 1

Local server, run it on your machine

Nasdaq Data Link (community) runs locally over stdio. You need Node.js (for npx) or Python (for uvx) installed, then add the command below to your client's MCP config file.

Command

uv run mcp install nasdaq_data_link_mcp_os/server.py --env-file .env --name " Nasdaq Data Link MCP Server " --with nasdaq-data-link --with pycountry

Client config snippet

{
  "mcpServers": {
    "09369e2c-63ea-4fa7-8df5-1a674774648a": {
      "command": "uv",
      "args": [
        "run",
        "mcp",
        "install",
        "nasdaq_data_link_mcp_os/server.py",
        "--env-file",
        ".env",
        "--name",
        "\"",
        "Nasdaq",
        "Data",
        "Link",
        "MCP",
        "Server",
        "\"",
        "--with",
        "nasdaq-data-link",
        "--with",
        "pycountry"
      ]
    }
  }
}

Step 2

Authenticate with API key

Create a key in the vendor's dashboard and store it as an environment variable in your client config. Never paste it into a chat window.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Market & Financial Data.

Tax-lot and wash-sale check

A flag list before trades are placed.

Trade & RebalanceCustody & ClearingMarket & Financial Data

Read-only: for the proposed sells in <account>, review tax lots at the custodian and flag short-term gains, large realised gains, and any purchase in the last 30 days that could create a wash sale. Then use market-data tools to value each lot at the latest available price and to check for splits, mergers or other corporate actions that would change basis or share count. Output Symbol / Lot / Acquired / Basis / Market value / Gain-loss / Flag / Source. Do not place or modify trades. Tell me where the data may be delayed or incomplete.

Guardrail · Read-only. Confirm lot data with the custodian before acting on it.

Scenario comparison brief

A side-by-side read on two planning scenarios.

Financial PlanningFinancial PlanningMarket & Financial Data

Read-only: compare the existing plan for <client name> against the scenario <describe change, e.g. retire two years earlier>. Pull the plan's stored return, inflation and yield assumptions, then use market-data tools to show current comparable figures for the same inputs. Present outcome differences, an assumptions table of Plan assumption / Current market reading / Source / Date, and which assumption the result is most sensitive to. State every assumption explicitly. Do not save, overwrite or publish any scenario in the planning system.

Guardrail · Read-only. Plan illustrations are not advice, review before sharing.

Market context talking points

Three to five neutral talking points on recent market moves.

Client Review Meeting PrepWealth PlatformsMarket & Financial Data

Read-only: pull <client name>'s current holdings and sector or asset-class weights from the wealth platform, then use market-data tools to explain what moved those specific exposures over the last quarter. Return three to five neutral talking points, each tied to a holding or weight and to the market data behind it. No forecasts, no recommendations to buy or sell, no performance promises. Cite the source and date for both the holdings figure and the market figure so I can verify before I use it with a client.

Guardrail · Educational framing only. Avoid forward-looking or promissory language.

Read the full connection guide →