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 ✓
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
- 复制上面的命令
- 粘成
claude_desktop_config.json里mcpServers的一项(本地服务器用 command + args,示例见 客户端接法) - 重启客户端
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"datavidence-datavidence-financials-mcp": {
"command": "uvx",
"args": ["datavidence-financials"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"datavidence-datavidence-financials-mcp": {
"command": "uvx",
"args": ["datavidence-financials"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio datavidence-datavidence-financials-mcp -- uvx datavidence-financials
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 0 ★ · datavidence/datavidence-financials-mcp · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 23 个来源 · mcp
- 安装
uvx datavidence-financials
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
uvx datavidence-financials。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
datavidence/datavidence-financials-mcp;我们收录于 2026-10-23;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/datavidence-datavidence-financials-mcp/)
- 来源
- awesome · https://github.com/datavidence/datavidence-financials-mcp
- 按领域浏览
- MCP 服务
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 该仓库根目录有
SECURITY.md(我们只核文件存在,未核内容)
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。