Skip to main content
mcpSource-backed
Financial Datasets logo

Financial Datasets MCP Server

Python MCP server that lets Claude query Financial Datasets for stock statements, prices, company news, crypto prices, and SEC filings.

Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/financial-datasets/mcp-server/blob/main/README.md, https://github.com/financial-datasets/mcp-server
Brand
Financial Datasets
Brand domain
financialdatasets.ai
Brand asset source
brandfetch
Safety notes
This server retrieves financial market data; do not treat tool output or model summaries as investment, trading, tax, or legal advice., Current prices, crypto prices, filings, and news can be delayed, incomplete, rate limited, or unavailable depending on API plan and market conditions., Review generated analysis before using it in portfolio decisions, trading workflows, client reports, or compliance-sensitive research., The server sends ticker symbols, date ranges, filing filters, and research queries to the Financial Datasets API.
Privacy notes
API keys must be stored in environment variables or local secret managers and never committed to configuration files., Queried tickers, crypto symbols, time ranges, filings, and news requests can reveal research interests, watchlists, client assignments, or trading hypotheses., Tool outputs may include financial statements, prices, filings, and news that become part of the model context and logs., Avoid sending private portfolio holdings, customer identifiers, or material non-public information through prompts or tool arguments.
Author
Financial Datasets
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

12 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first.

0/5 ready
Account & credentials1Install & runtime2General212 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.

4 areas
  • SafetyGeneralThis server retrieves financial market data; do not treat tool output or model summaries as investment, trading, tax, or legal advice.
  • SafetyGeneralCurrent prices, crypto prices, filings, and news can be delayed, incomplete, rate limited, or unavailable depending on API plan and market conditions.
  • SafetyGeneralReview generated analysis before using it in portfolio decisions, trading workflows, client reports, or compliance-sensitive research.
  • SafetyGeneralThe server sends ticker symbols, date ranges, filing filters, and research queries to the Financial Datasets API.
  • PrivacyCredentials & tokensAPI keys must be stored in environment variables or local secret managers and never committed to configuration files.
  • PrivacyNetwork accessQueried tickers, crypto symbols, time ranges, filings, and news requests can reveal research interests, watchlists, client assignments, or trading hypotheses.
  • PrivacyData retentionTool outputs may include financial statements, prices, filings, and news that become part of the model context and logs.
  • PrivacyGeneralAvoid sending private portfolio holdings, customer identifiers, or material non-public information through prompts or tool arguments.

Disclosure: Uses the Financial Datasets API, which may require an account, API key, and plan-specific usage limits.

Safety notes

  • This server retrieves financial market data; do not treat tool output or model summaries as investment, trading, tax, or legal advice.
  • Current prices, crypto prices, filings, and news can be delayed, incomplete, rate limited, or unavailable depending on API plan and market conditions.
  • Review generated analysis before using it in portfolio decisions, trading workflows, client reports, or compliance-sensitive research.
  • The server sends ticker symbols, date ranges, filing filters, and research queries to the Financial Datasets API.

Privacy notes

  • API keys must be stored in environment variables or local secret managers and never committed to configuration files.
  • Queried tickers, crypto symbols, time ranges, filings, and news requests can reveal research interests, watchlists, client assignments, or trading hypotheses.
  • Tool outputs may include financial statements, prices, filings, and news that become part of the model context and logs.
  • Avoid sending private portfolio holdings, customer identifiers, or material non-public information through prompts or tool arguments.

Prerequisites

  • Python 3.11 or newer, matching the upstream project metadata.
  • uv installed on the machine running the MCP server.
  • A cloned checkout of `financial-datasets/mcp-server`.
  • Financial Datasets API key stored as `FINANCIAL_DATASETS_API_KEY`.
  • Understanding of the Financial Datasets API plan, rate limits, market-data coverage, and terms.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
12 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Uses the Financial Datasets API, which may require an account, API key, and plan-specific usage limits.
Full copyable content
{
  "mcpServers": {
    "financial-datasets": {
      "command": "uv",
      "args": ["--directory", "PATH_TO_FINANCIAL_DATASETS_MCP", "run", "server.py"],
      "env": {
        "FINANCIAL_DATASETS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

About this resource

Content

Financial Datasets MCP Server is a Python FastMCP server that connects Claude and other MCP clients to the Financial Datasets stock market API. The upstream README describes tools for retrieving company financial statements, stock prices, market news, crypto prices, and SEC filings through a stdio MCP server.

The server loads FINANCIAL_DATASETS_API_KEY from the environment, sends API requests to the Financial Datasets API, and returns JSON-formatted tool results to the MCP client.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository, README, source file, project metadata, environment example, and API pages for current tool names, setup requirements, API endpoints, and usage limits.

Features

  • Retrieve income statements for a ticker.
  • Retrieve balance sheets for a ticker.
  • Retrieve cash flow statements for a ticker.
  • Retrieve the current or latest stock price for a ticker.
  • Retrieve historical stock prices by ticker, date range, interval, and interval multiplier.
  • Retrieve company news by ticker.
  • List available crypto tickers.
  • Retrieve current and historical crypto prices.
  • Retrieve SEC filings by ticker, limit, and optional filing type.
  • Run as a stdio MCP server through uv run server.py.

Installation

Clone the repository and install dependencies with uv following the upstream README. Create a local environment file or configure the MCP client environment with FINANCIAL_DATASETS_API_KEY.

For MCP clients that launch stdio servers:

{
  "mcpServers": {
    "financial-datasets": {
      "command": "uv",
      "args": ["--directory", "PATH_TO_FINANCIAL_DATASETS_MCP", "run", "server.py"],
      "env": {
        "FINANCIAL_DATASETS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Restart the MCP client after adding the server, then test with a low-risk ticker lookup before using it for a larger research workflow.

Use Cases

  • Ask Claude to summarize recent income statements for a public company.
  • Compare balance sheet and cash flow trends over several periods.
  • Retrieve current and historical prices for a ticker before building a research note.
  • Pull recent company news alongside financial statement context.
  • Gather SEC filing metadata for a ticker and filing type.
  • Retrieve crypto price history for supported symbols.

Safety and Privacy

Financial Datasets MCP Server is useful for research, but market-data tooling is not a substitute for professional financial advice, official filings, broker records, or compliance-reviewed analysis. Treat model-generated conclusions as draft research, verify source data independently, and avoid using automated outputs directly in trading, client recommendations, or regulatory reporting.

Keep the Financial Datasets API key out of repositories and shared logs. Ticker queries, filing filters, date ranges, and news searches can reveal research targets or trading intent, so avoid including private portfolio details, customer identifiers, or material non-public information in prompts.

Duplicate Check

Existing entries cover other financial-data and finance-adjacent MCP servers, but no financial-datasets/mcp-server, Financial Datasets API MCP entry, or matching source URL was found in content/mcp.

Source citations

Add this badge to your README

Show that Financial Datasets MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/financial-datasets-mcp-server.svg)](https://heyclau.de/entry/mcp/financial-datasets-mcp-server)

How it compares

Financial Datasets MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field

Python MCP server that lets Claude query Financial Datasets for stock statements, prices, company news, crypto prices, and SEC filings.

Open dossier

Access high-quality fundamental financial data from SEC filings and investor presentations

Open dossier

Streamable HTTP MCP server for financial research workflows, including standardized financial data, SEC filing search, company discovery, market signals, ticker resolution, and alternative-data table exploration.

Open dossier

Inferventis hosted MCP server with 20 financial tools for FX rates, stocks, crypto, news, and URL reading over streamable HTTP, with many free tools and optional premium API keys.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustDiffersPackage not verifiedPackage verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedNo submission linkSource-backedSubmission linkedSource submission
SubmitterDiffersoktofeesh1oktofeesh1kiannidev
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandFinancial Datasets logoFinancial DatasetsDaloopa logoDaloopaDrillr logoDrillr
Categorymcpmcpmcpmcp
SourceSource-backedFirst-partySource-backedSource-backed
AuthorFinancial DatasetsDaloopaDrillrInferventis
Added2026-06-052025-09-182026-06-052026-06-14
Platforms
Harness
Source repo
Safety notesThis server retrieves financial market data; do not treat tool output or model summaries as investment, trading, tax, or legal advice. Current prices, crypto prices, filings, and news can be delayed, incomplete, rate limited, or unavailable depending on API plan and market conditions. Review generated analysis before using it in portfolio decisions, trading workflows, client reports, or compliance-sensitive research. The server sends ticker symbols, date ranges, filing filters, and research queries to the Financial Datasets API.Treat financial data as informational research and verify figures before using them for investment, accounting, or reporting decisions.Drillr's MCP endpoint is a remote Streamable HTTP server at `https://gateway.drillr.ai/mcp/data` and requires a bearer API key. Tool calls can consume Drillr credits or billable API usage. Check plan limits and remaining credit balance before high-volume research loops. run_sql is documented as read-only SELECT access, but broad queries across 90-plus tables can still be expensive, slow, or noisy. Treat outputs as research inputs, not investment, legal, accounting, tax, or trading advice. Drillr documents that it does not place trades, manage brokerage positions, expose options chains, or provide its own price forecasts. Review cited SEC filing paragraphs, table schemas, ticker resolution, and source coverage before relying on results in reports or decisions.Makes outbound network requests to Inferventis and third-party financial data providers. URL reader tools fetch arbitrary web pages; treat returned content as untrusted. Premium tools may incur API usage charges when keys are configured. Do not rely on MCP output for automated trading without independent verification.
Privacy notesAPI keys must be stored in environment variables or local secret managers and never committed to configuration files. Queried tickers, crypto symbols, time ranges, filings, and news requests can reveal research interests, watchlists, client assignments, or trading hypotheses. Tool outputs may include financial statements, prices, filings, and news that become part of the model context and logs. Avoid sending private portfolio holdings, customer identifiers, or material non-public information through prompts or tool arguments.Company queries, filing references, financial models, and research topics may be sent through the MCP client and model.Prompts, ticker lists, research themes, SQL queries, and retrieved financial context are sent to Drillr's hosted gateway and the connected MCP client. Drillr API keys are sensitive credentials. Keep them out of prompts, shared configs, issue comments, logs, screenshots, and repository files. Research prompts may reveal portfolio interests, watchlists, investment theses, client names, diligence topics, or confidential strategy. SEC filing excerpts, analyst consensus, alt-data, market signals, and generated summaries may be retained by MCP clients, AI providers, logs, or downstream tools. Use synthetic prompts or public tickers for demos, screenshots, and examples when client, portfolio, or internal research strategy is sensitive.Ticker symbols, URLs, and search queries you send are processed by Inferventis and upstream data vendors. Premium API keys are credentials; store them in MCP headers or env vars, not in chat or source control. Fetched page content may include tracking parameters from the original URL.
Prerequisites
  • Python 3.11 or newer, matching the upstream project metadata.
  • uv installed on the machine running the MCP server.
  • A cloned checkout of `financial-datasets/mcp-server`.
  • Financial Datasets API key stored as `FINANCIAL_DATASETS_API_KEY`.
  • Daloopa account with active subscription
  • Daloopa API key (obtained from Daloopa sales team - contact sales@daloopa.com)
  • Internet connection for accessing Daloopa MCP server (https://mcp.daloopa.com/server/mcp)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Drillr account at `https://drillr.ai`.
  • External-scope Drillr API key from `https://drillr.ai/developer/keys`.
  • MCP client that supports Streamable HTTP servers with bearer headers.
  • Secure secret storage for `DRILLR_API_KEY` outside prompts, repository files, screenshots, and shell history.
  • Claude Pro, Team, or Enterprise with Connectors support, or Claude Code with HTTP MCP transport.
  • Internet access to reach the Inferventis Cloud Run endpoint in europe-west1.
  • Optional Inferventis API key for premium market data tools that require authentication.
  • Awareness that financial data is informational and not investment advice.
Install
uv run server.py
claude mcp list && claude mcp status daloopa
claude mcp add drillr https://gateway.drillr.ai/mcp/data --transport http --header "Authorization: Bearer $DRILLR_API_KEY"
claude mcp add --transport http inferventis https://mcp-server-295985738387.europe-west1.run.app/mcp
Config
{
  "mcpServers": {
    "financial-datasets": {
      "command": "uv",
      "args": ["--directory", "PATH_TO_FINANCIAL_DATASETS_MCP", "run", "server.py"],
      "env": {
        "FINANCIAL_DATASETS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "daloopa": {
      "url": "https://mcp.daloopa.com/server/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "drillr": {
      "type": "http",
      "url": "https://gateway.drillr.ai/mcp/data",
      "headers": {
        "Authorization": "Bearer ${DRILLR_API_KEY}"
      }
    }
  }
}
{
  "mcpServers": {
    "inferventis": {
      "url": "https://mcp-server-295985738387.europe-west1.run.app/mcp",
      "type": "http",
      "headers": {
        "X-API-Key": "YOUR_INFERVENTIS_KEY"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.