D
datavidence/datavidence-financials-mcp
Open-source Model Context Protocol (MCP) server for the Datavidence Financials API. Gives LLM agents normalized US-GAAP financial statements from SEC EDGAR - income statement, balance sheet, cash flow - with point-in-time (as-reported) figures and per-value SEC source provenance for citation.
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"datavidence-datavidence-financials-mcp": {
"command": "uvx",
"args": ["datavidence-financials"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"datavidence-datavidence-financials-mcp": {
"command": "uvx",
"args": ["datavidence-financials"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio datavidence-datavidence-financials-mcp -- uvx datavidence-financials
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 0 ★ · datavidence/datavidence-financials-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 23 sources · mcp
- Install
uvx datavidence-financials
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uvx datavidence-financials. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
datavidence/datavidence-financials-mcp；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Datavidence Financials — MCP Server
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Normalized US-GAAP financial statements for every SEC XBRL filer — point-in-time, as originally reported — as MCP tools for your AI agent (or a plain REST API).
Language models are good at reasoning about financial statements and bad at getting them. SEC EDGAR has the data, but its XBRL is a thicket of inconsistent tags, renamed concepts, and per-filer quirks — so agents either hallucinate the numbers or you spend weeks building a normalization layer. This is that layer: your agent asks for a company's financials and gets a clean, consistent answer — over the Model Context Protocol, or as a plain REST API.
> ⭐ If this is useful, please star the repo. It's a solo, early project, and stars are how other developers find it.
This is the open-source, AI-native layer for the Datavidence Financials API — a standalone stdio server that forwards over HTTPS to the REST API (bring your own key). The connector is MIT-licensed; the underlying API is a commercial service.
## Try it in 30 seconds (no signup)
Run it with no clone using uv — it installs into a throwaway environment:
bash
FLAPIKEY=sandboxdemokey uvx datavidence-financials
sandboxdemokey returns sample data with no signup — good for a first run. Set FLAPIKEY to your real key for live SEC data. The server speaks MCP over stdio, so an MCP client (e.g. Claude Desktop, below) launches it.
Or install it as a persistent tool with pipx:
bash
pipx install datavidence-financials
FLAPIKEY=sandboxdemokey datavidence-financials
## Connect by URL (no install)
Clients that support remote MCP servers (streamable HTTP) can connect without installing anything:
| URL | Key | Data |
| https://mcp.financials.datavidence.ai/mcp | none | sample (AAPL FY2023) |
| https://mcp.financials.datavidence.ai/rapidapi/mcp | your RapidAPI key, as X-API-Key or Authorization: Bearer | live SEC data, metered by RapidAPI against your plan |
Claude Code:
bash
claude mcp add --transport http datavidence-financials \
https://mcp.financials.datavidence.ai/rapidapi/mcp \
--header "X-API-Key: YOURRAPIDAPIKEY"
For the sample data, use the /mcp URL and leave out the header.
claude.ai: add https://mcp.financials.datavidence.ai/mcp as a custom connector with no sign-in. claude.ai can't send an API key for most accounts yet, so it gets the sample data for now.
## Why it's different
Point-in-time, as originally reported. Pass an asof date and you get the figures as they stood then — no look-ahead bias from later restatements. The thing backtests quietly get burned without.
Normalized to one schema. EDGAR's XBRL tags drift between filers and change over the years. We map them to a single US-GAAP income statement, balance sheet, and cash flow — including the awkward cases (noncontrolling interest, mezzanine/temporary equity, non-calendar fiscal years) — so you never parse a filing.
Every SEC XBRL filer. Coverage is the whole SEC XBRL universe (~2009 to present), fetched and normalized on demand — any CIK with XBRL facts, not a curated subset.
Source-linked, too. Turn on provenance and every value carries its SEC accession, filed date, and a direct EDGAR URL — so the model cites the filing instead of inventing a number.
Language models are good at reasoning about financial statements and bad at getting them. SEC EDGAR has the data, but its XBRL is a thicket of inconsistent tags, renamed concepts, and per-filer quirks — so agents either hallucinate the numbers or you spend weeks building a normalization layer. This is that layer: your agent asks for a company's financials and gets a clean, consistent answer — over the Model Context Protocol, or as a plain REST API.
> ⭐ If this is useful, please star the repo. It's a solo, early project, and stars are how other developers find it.
This is the open-source, AI-native layer for the Datavidence Financials API — a standalone stdio server that forwards over HTTPS to the REST API (bring your own key). The connector is MIT-licensed; the underlying API is a commercial service.
## Try it in 30 seconds (no signup)
Run it with no clone using uv — it installs into a throwaway environment:
bash
FLAPIKEY=sandboxdemokey uvx datavidence-financials
sandboxdemokey returns sample data with no signup — good for a first run. Set FLAPIKEY to your real key for live SEC data. The server speaks MCP over stdio, so an MCP client (e.g. Claude Desktop, below) launches it.
Or install it as a persistent tool with pipx:
bash
pipx install datavidence-financials
FLAPIKEY=sandboxdemokey datavidence-financials
## Connect by URL (no install)
Clients that support remote MCP servers (streamable HTTP) can connect without installing anything:
| URL | Key | Data |
| https://mcp.financials.datavidence.ai/mcp | none | sample (AAPL FY2023) |
| https://mcp.financials.datavidence.ai/rapidapi/mcp | your RapidAPI key, as X-API-Key or Authorization: Bearer | live SEC data, metered by RapidAPI against your plan |
Claude Code:
bash
claude mcp add --transport http datavidence-financials \
https://mcp.financials.datavidence.ai/rapidapi/mcp \
--header "X-API-Key: YOURRAPIDAPIKEY"
For the sample data, use the /mcp URL and leave out the header.
claude.ai: add https://mcp.financials.datavidence.ai/mcp as a custom connector with no sign-in. claude.ai can't send an API key for most accounts yet, so it gets the sample data for now.
## Why it's different
Point-in-time, as originally reported. Pass an asof date and you get the figures as they stood then — no look-ahead bias from later restatements. The thing backtests quietly get burned without.
Normalized to one schema. EDGAR's XBRL tags drift between filers and change over the years. We map them to a single US-GAAP income statement, balance sheet, and cash flow — including the awkward cases (noncontrolling interest, mezzanine/temporary equity, non-calendar fiscal years) — so you never parse a filing.
Every SEC XBRL filer. Coverage is the whole SEC XBRL universe (~2009 to present), fetched and normalized on demand — any CIK with XBRL facts, not a curated subset.
Source-linked, too. Turn on provenance and every value carries its SEC accession, filed date, and a direct EDGAR URL — so the model cites the filing instead of inventing a number.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/datavidence-datavidence-financials-mcp/)
- Source
- awesome · https://github.com/datavidence/datavidence-financials-mcp
- Browse by field
- MCP servers
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.