B
Blahaj-gif/Finance-mcp
An MCP server that gives an AI assistant read access to your real brokerage
★ 3·更新 2026-11-06
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 3 ★ · Blahaj-gif/Finance-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Blahaj-gif/Finance-mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Finance MCP
以下摘录自该仓库的 README(片段)
An MCP server that gives an AI assistant read access to your real brokerage
account and the market around it — and gives you, not the assistant, the only
button that sends an order.
38 tools over Webull, Saxo, IBKR, Yahoo Finance, SEC EDGAR, BLS, the Federal
Reserve and the BEA, plus a Streamlit dashboard that is the sole path to
execution. The list is filtered to what your broker can actually serve, so a
given account sees 36 or 37 of them — and 28 with no broker at all, which
is a working install, not a broken one.
The assistant can draft an order. It cannot place one. Drafts go to a local
queue; sending requires a broker preview and your click in the dashboard. That
path does not exist on the tool side, so no prompt can reach it.
Every tool declares this to the client rather than only to the reader: 32 of
36 are annotated read-only, one is destructive (cancel_order, which pulls a
resting order). A client that respects MCP annotations can wave through a price
lookup and stop on the one call that reaches the market.
### What this can and cannot do with your account
Asking an unknown repository for brokerage credentials is the hardest trust ask
in software, so the answer is here rather than forty paragraphs down.
There is no execution path on the tool side. Not gated, not guarded —
absent. draft_order writes to a local queue. Sending needs a broker preview
and your click in the dashboard, which no prompt can reach.
Twenty-eight of the 38 tools never touch a broker. SEC filings, macro,
indicators, options maths, earnings. With no credentials at all you get those
twenty-eight, and that is a working install rather than a degraded one.
Two of the three adapters have never been run. Saxo and Interactive
Brokers are built from published API references and have not been executed
against a live or paper account. They say so in every tool output that uses
them. Only Webull has been run against a real account.
The dashboard's submit button is Webull-only. The MCP tools route through
the broker protocol; that one button does not, yet.
Use a read-scoped key where your broker offers one. Nothing outside the
dashboard needs write access.
1,431 tests across 32 files, and CI runs them on every push.
Those all stub the network, which is correct — a suite that goes red because SEC
returned a 503 overnight is a suite nobody reads. It is also why two defects
survived every one of them: a euro-area series that had stopped publishing eight
months earlier and was reported as current, and a filing watcher that answered
403 to every request and called itself healthy. Both needed the real internet to
see. tests/test_live_sources.py asks every external source for real and checks
that this tool's account of the answer is true — in particular that a series
marked fresh actually is. It is opt-in and skipped by default:
FINANCE_LIVE_SOURCES=1 pytest tests/test_live_sources.py -v -s
It also runs weekly in CI, because a check that depends on somebody remembering
is a check that eventually stops happening — and discontinued series and broken
scrapers are exactly the failures that arrive quietly over weeks. That workflow
is inert until FRED_API_KEY and SEC_USER_AGENT exist as repository secrets,
account and the market around it — and gives you, not the assistant, the only
button that sends an order.
38 tools over Webull, Saxo, IBKR, Yahoo Finance, SEC EDGAR, BLS, the Federal
Reserve and the BEA, plus a Streamlit dashboard that is the sole path to
execution. The list is filtered to what your broker can actually serve, so a
given account sees 36 or 37 of them — and 28 with no broker at all, which
is a working install, not a broken one.
The assistant can draft an order. It cannot place one. Drafts go to a local
queue; sending requires a broker preview and your click in the dashboard. That
path does not exist on the tool side, so no prompt can reach it.
Every tool declares this to the client rather than only to the reader: 32 of
36 are annotated read-only, one is destructive (cancel_order, which pulls a
resting order). A client that respects MCP annotations can wave through a price
lookup and stop on the one call that reaches the market.
### What this can and cannot do with your account
Asking an unknown repository for brokerage credentials is the hardest trust ask
in software, so the answer is here rather than forty paragraphs down.
There is no execution path on the tool side. Not gated, not guarded —
absent. draft_order writes to a local queue. Sending needs a broker preview
and your click in the dashboard, which no prompt can reach.
Twenty-eight of the 38 tools never touch a broker. SEC filings, macro,
indicators, options maths, earnings. With no credentials at all you get those
twenty-eight, and that is a working install rather than a degraded one.
Two of the three adapters have never been run. Saxo and Interactive
Brokers are built from published API references and have not been executed
against a live or paper account. They say so in every tool output that uses
them. Only Webull has been run against a real account.
The dashboard's submit button is Webull-only. The MCP tools route through
the broker protocol; that one button does not, yet.
Use a read-scoped key where your broker offers one. Nothing outside the
dashboard needs write access.
1,431 tests across 32 files, and CI runs them on every push.
Those all stub the network, which is correct — a suite that goes red because SEC
returned a 503 overnight is a suite nobody reads. It is also why two defects
survived every one of them: a euro-area series that had stopped publishing eight
months earlier and was reported as current, and a filing watcher that answered
403 to every request and called itself healthy. Both needed the real internet to
see. tests/test_live_sources.py asks every external source for real and checks
that this tool's account of the answer is true — in particular that a series
marked fresh actually is. It is opt-in and skipped by default:
FINANCE_LIVE_SOURCES=1 pytest tests/test_live_sources.py -v -s
It also runs weekly in CI, because a check that depends on somebody remembering
is a check that eventually stops happening — and discontinued series and broken
scrapers are exactly the failures that arrive quietly over weeks. That workflow
is inert until FRED_API_KEY and SEC_USER_AGENT exist as repository secrets,
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/blahaj-gif-finance-mcp/)
- 来源
- awesome · https://github.com/Blahaj-gif/Finance-mcp
- 按领域浏览
- MCP 服务
- Traction
- 3 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。