_ registry / mcp http-sse · checked 10h ago

FinLab

https://mcp.finlab.finance

Registry code: 2d4da9f173faeb3b

api record

FinLab（finlab.finance）是台股量化投資平台：提供台股量化數據、每日更新的個股實證訊號、以及以 finlab Python 套件實跑的真實回測策略庫。本 MCP server 只讀公開數據。可查詢：策略庫清單與完整策略（含 Python 程式碼）、個股體質與訊號實證（如 2330 台積電）、資料庫目錄摘要、FinLab Skill 開發文件（get_finlab_docs，撰寫 finlab 程式前先查）、以及 FinLab 快速上手方式。所有數據僅供研究參考，不構成投資建議。

endpoint
https://mcp.finlab.finance/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
718ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_data_catalog open 10h ago

    取得 FinLab 量化資料庫的目錄摘要：涵蓋台股與美股的分類數、欄位數、資料列數、年份範圍，以及代表性資料集（股價、月營收、財務指標等）。適合回答「FinLab 有哪些資料」。

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_finlab_docs open 10h ago

    取得 FinLab Skill 的開發文件（與 GitHub koreal6803/finlab-ai main 分支同步，skill 更新後自動生效）：不帶參數回傳 SKILL.md 主文件與參考文件清單；帶 doc 參數回傳指定參考文件全文。涵蓋 900+ 資料欄位、sim() 回測 API、60+ 策略範例、因子分析與機器學習等，撰寫 finlab Python 程式前建議先查閱。

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "doc": {
      "type": "string",
      "description": "參考文件檔名，例如 \"dataframe-reference.md\"。省略時回傳 SKILL.md 與文件清單。"
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • list_strategies open 10h ago

    列出 FinLab 公開策略庫中的台股量化策略，含每一檔策略的真實回測績效摘要（CAGR、Sharpe、最大回撤）與基準比較。想看完整策略內容與 Python 程式碼時，請接著呼叫 get_strategy。

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_strategy unknown never probed

    取得 FinLab 策略庫中單一策略的完整快照：策略說明、真實回測績效與基準比較、以及可直接執行的 finlab Python 程式碼。slug 可先用 list_strategies 查詢。

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "策略代號（slug），例如由 list_strategies 取得"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_stock_evidence unknown never probed

    查詢台股個股的每日更新數據實證：基本面體質定位（獲利、估值、籌碼因子百分位）、目前正在觸發的量化訊號與其歷史前瞻報酬統計、估值位階等。例如 symbol="2330" 查台積電。資料來自 FinLab 每日以 finlab 套件計算的真實數據。

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "symbol"
  ],
  "properties": {
    "market": {
      "enum": [
        "tw",
        "us"
      ],
      "type": "string",
      "description": "市場，預設 \"tw\" 台股；\"us\" 為美股（覆蓋率較低）。"
    },
    "symbol": {
      "type": "string",
      "description": "台股股票代號字串，例如 \"2330\"（台積電）、\"0050\"、\"00631L\"。保留前導零，不要轉成數字。"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • how_to_start unknown never probed

    取得 FinLab 快速上手指南：如何用 AI 輔助流程（Claude cowork / Codex）在自己電腦安裝 FinLab 並跑第一個台股策略真實回測，以及免費線上體驗入口。適合回答「怎麼開始用 FinLab」「怎麼回測台股」。

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2d4da9f173faeb3b/badge.svg)](https://brick.blue/agent/2d4da9f173faeb3b)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.