Daepak Market Intelligence

io.github.Mobiss11由 GitHub 账号 Mobiss11 发布v2.1.1更新于 Oct 25, 2026

Market analyst tools + AI agent: crypto, US equities, options, Korea, fundamentals, macro, backtests

已验证Streamable HTTP可网页运行金融数据与分析

概览

AI 生成的概览

Daepak Market Intelligence 为助手提供市场分析工具和 AI 智能体，覆盖加密货币、美股、韩国市场、期权、宏观与回测。

可以做什么
加密货币与代币数据：价格、K 线、支撑阻力位、指标、评分、衍生品、订单簿、爆仓、恐惧贪婪指数，以及任意代币查询与持有者。美股与韩国市场：报价、历史、价位、持有者、涨跌榜、停牌、泡菜溢价、KRX 筛选与 ETF。基本面与宏观：OpenDART 与 SEC 财报、跨市场对比、FRED 快照与序列。期权与验证：隐含波动率指标、持仓、收益与希腊值、回测、信号结果与命中率。研究：新闻与叙事检索、抓取网址、网页搜索。个人记录：持仓、投资组合、交易日志、催化剂与记忆，读写权限分开。分析智能体可回答问题并流式输出。
适用场景
当助手需要跨加密货币、美股、韩国股票、期权和宏观的市场数据与分析，或需要调用厂商的分析智能体并维护交易日志时使用。免费套餐的每月额度足以试用。
运行要求
可使用远程端点并在浏览器中通过 OAuth 登录，也可用 uvx 或 pip 从 PyPI 包 daepak-mcp 在本地运行。本地方式需要环境变量 DAEPAK_API_KEY，需从厂商的 Keys 页面获取。可选设置为 DAEPAK_BASE_URL 和 DAEPAK_TIMEOUT。需要网络访问。
安装前请注意
API 密钥是敏感凭据，以 bearer 方式发送，不要写入共享配置。调用会消耗套餐内的额度，并受每分钟和每月上限限制。写入权限的工具会修改交易日志、投资组合等个人记录。市场数据可能过期，README 也提醒胜率和泡菜溢价的解读容易出错。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Daepak Market Intelligence，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.Mobiss11%2Fdaepak-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "daepak-market-intelligence": {
      "type": "http",
      "url": "https://daepak.com/mcp"
    }
  }
}

README

Daepak MCP

Market intelligence tools for any MCP-capable engine — Claude Code, Claude Desktop, or your own agent. Prices, indicators, levels, positioning, the Korean market, US equities, options, backtests, macro (FRED), SEC and OpenDART fundamentals, and your own trading journal. 108 tools, the same ones the product's own analyst uses.

The server describes nothing itself: it pulls the catalogue from GET /v1/tools, so it shows exactly what your key is allowed to call and never drifts from the product.

Quick start

No install — remote server (recommended)

The same tools are served at https://daepak.com/mcp (Streamable HTTP) with OAuth 2.1: you sign in once in the browser, no key to copy.

bash
claude mcp add --transport http daepak https://daepak.com/mcp

Then /mcp inside Claude Code → daepak → Authenticate. Works the same way as a custom connector in Claude.ai (paste the URL) and in ChatGPT developer mode. For Codex CLI:

toml
[mcp_servers.daepak]url = "https://daepak.com/mcp"

Prefer a key instead of OAuth (servers, CI)? Send it as a header:

bash
claude mcp add --transport http daepak https://daepak.com/mcp --header "Authorization: Bearer dpk_live_…"

Local (stdio)

bash
claude mcp add daepak -e DAEPAK_API_KEY=dpk_live_… -- uvx daepak-mcp

Or install it yourself:

bash
pip install daepak-mcp

Get a key on the Keys page of your profile at daepak.com. The free plan includes 2 000 credits a month — enough to build something over an evening.

Configuration

variabledefaultpurpose
DAEPAK_API_KEY—your key, dpk_live_…. Required.
DAEPAK_BASE_URLhttps://daepak.compoint at another environment
DAEPAK_TIMEOUT120seconds per call

Nothing else is read. In particular there is no setting that names a user: the account is derived from the key, and a request cannot claim to be someone else.

What you get

The catalogue is filtered by your key's scopes — you never see a tool you cannot call.

scopetoolswhat it opens
read:market88prices, candles, indicators, levels, scores, narratives, derivatives, order book, liquidations, options, US equities, Korean market, fundamentals (OpenDART, SEC), macro (FRED), backtests
read:personal9your positions, portfolio, trade journal, catalysts, memory, background tasks
write:personal11writing to those same records
agent:chat—full analyst answers, streamed or complete

Being allowed to read your journal does not allow writing to it. That is a separate scope.

Crypto — get_price, get_price_history, get_levels (support/resistance, Fibonacci, ATR — computed, not drawn), get_indicators, get_score, get_regime, get_derivatives, get_orderbook, get_liquidations, get_fear_greed

Korea — get_kimchi_premium (the Upbit-to-global spread, decomposed into the asset leg and the currency leg), Korean tickers, fresh Upbit listings

US equities — get_stock_quote, get_stock_history, get_stock_levels, get_stock_holders (institutions and insiders), get_us_gap_stats, get_us_movers, get_us_halts, get_us_insiders

Fundamentals from primary sources — get_kr_financials (K-IFRS for any KRX listing, OpenDART), get_us_financials (US-GAAP and IFRS by fiscal year from SEC EDGAR, up to 20 years), compare_financials (Korean and US companies in one schema, USD at the FRED rate), get_kr_insiders, screen_kr (the whole KRX with RS percentiles and foreign-ownership flow), get_kr_rs, list_kr_etfs, backtest_kr_portfolio (against KOSPI)

Macro — get_macro_snapshot (Fed funds, US 2Y/10Y and the curve, broad dollar, USD/KRW, VIX, CPI as YoY, unemployment, Korean overnight rate), get_macro_series (any FRED id with history). Every row carries stale_days; Korean CPI is absent on purpose — FRED's series died in 2023.

Options — get_iv_metrics, get_options_positioning, get_option_structure (payoff and greeks), get_options_backtest

Validation — get_backtest, get_signal_outcomes, get_hit_rate, get_score_history

Arbitrary tokens — resolve_token, get_token_market, get_token_onchain, get_token_holders, for anything outside the watchlist

Research — search_news (RAG over the collected corpus), search_narratives, fetch_url, web_search

The agent

The same analyst that answers in the product, over HTTP. It has everything the chat has:

POST /v1/agent/streamserver-sent events — text arrives as it is written
POST /v1/agent/messagesthe complete answer in one response
GET /v1/agent/resume/{id}reconnect to a generation already running
POST /v1/agent/cancel/{id}stop one
GET /v1/agent/conversationsyour conversations, and /{id} for the messages
bash
curl -N -X POST https://daepak.com/v1/agent/stream \     -H "Authorization: Bearer dpk_live_…" -H "Content-Type: application/json" \     -d '{"message": "How does BTC look right now?", "mode": "mentor"}'

Conversation memory. The first event carries conversation_id; pass it back and the context continues.

Images. images takes data-URLs, exactly like chat attachments — the agent reads charts and screenshots.

Mentor mode. mode: "mentor" explains how the reading was arrived at, not just the conclusion.

⚠️ A dropped connection loses nothing. Generation continues in the background, the answer still lands in the conversation, and resume replays what you missed. Keep the conversation_id from the first event — that is where you reconnect.

⚠️ suggest (follow-up questions) arrives after done. A client that stops reading at done will never see it. The order is deliberate: the spinner should stop before the suggestions are computed.

Credits

Every tool declares its price in the catalogue, so a sequence can be budgeted before it runs. Prices come from measuring the tools in production, not from guessing:

tierwhatcredits
our databaseprices, indicators, levels, candles, narratives1
external callequities, tokens, options, on-chain5
embedding, sandboxnews search, code execution20

A tool nobody has priced yet costs 5, not 1 — an unpriced tool is either an oversight or something heavy, and both are safer to over-charge than to give away.

bash
curl -H "Authorization: Bearer dpk_live_…" https://daepak.com/v1/usage

When the monthly credits run out you get 402 naming two ways forward: a higher plan or the renewal at the start of the month. There is no overage billing — we would rather refuse than send an invoice nobody expected.

Using the API directly

The MCP server is a thin shell over a plain REST API.

bash
# catalogue: schema, scope and price for every tool your key can callcurl -H "Authorization: Bearer dpk_live_…" https://daepak.com/v1/tools
# call onecurl -X POST https://daepak.com/v1/tools/get_price \     -H "Authorization: Bearer dpk_live_…" \     -H "Content-Type: application/json" \     -d '{"coin": "BTC"}'
json
{  "tool": "get_price",  "credits_used": 1,  "credits_left": 1999,  "took_ms": 104,  "data": { "coin": "BTC", "price": 78017.26, "change_24h": -1.2 }}

Full reference: daepak.com/reference · OpenAPI 3.1: /v1/openapi.json (106 operations, no key needed to read it).

Reading the answers honestly

A few things the data will tell you if you look, and which are easy to get wrong:

  • Compare against the baseline, not against zero. "68 % of directions guessed" means nothing until you know what a random entry at the same moment would have given.
  • Win rate is not money. On our own data 68 % correct directions produced a profit factor of 1.04.
  • Groups under 30 observations are flagged reliable=false. That is an absence of a conclusion, not a weak one.
  • The kimchi premium has two legs — a discount on the asset and a discount on the won. Read together they mislead. And they explain rather than predict: on horizons up to a day we found no relationship (646 episodes).
  • Every answer carries the age of its data. If it is stale, say so rather than passing yesterday off as now.

Troubleshooting

401 — the key is missing, revoked, or malformed. Send it as Authorization: Bearer dpk_live_….

403 scope_required — the key lacks the scope; the response names which one.

400 user_id_not_accepted — the body contained a user_id. The account comes from the key; the field is rejected explicitly rather than ignored, so that a copied example fails loudly instead of quietly returning nothing.

404 conversation_not_found — that conversation belongs to another account.

429 — over the per-minute ceiling for your plan. The minute limit protects the service; the monthly one protects your budget.

CERTIFICATE_VERIFY_FAILED — you are running from source without certifi. Install the package instead of the file; the dependency exists for exactly this.

Error messages default to English; send X-Lang: ko or ru for those languages.

Links

License

MIT

来源：README.md，提交 c093174

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v2.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式必需10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分