原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

OneQAZ Trading Intelligence

作者:oneqaz-trading版本 1.3.0i★ 0i电脑或云端官方网站 ↗
注册名称io.github.wnsod/oneqaz-trading-mcp

安装方法

What it does

Verifiable crypto/KR/US market intelligence for AI agents: signals, hash-chained ledger. Not advice.

  • Connects 电脑或云端
  • Account or key Cloud: Works without a key · add X-API-Key if you have one (often raises limits) · Local: Needs PG_PASSWORD · 1 setting to fill in (PG_HOST)
  • Category 会计、财务与税务

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分15/100

质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 OneQAZ Trading Intelligence。按照 https://mcp.popnx.com/i/wnsod-oneqaz-trading-mcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/5 项检查 · 你的提问会经过开发者的服务器(api.oneqaz.com) · ✓ 命令已检查 2026年11月14日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称OneQAZ Trading Intelligence
    Remote MCP server URL · 地址https://api.oneqaz.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsOneQAZ Trading Intelligence

  4. 试一试

    用 OneQAZ Trading Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 OneQAZ Trading Intelligence,或回答中出现 OneQAZ Trading Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称OneQAZ Trading Intelligence
    Connection · 地址https://api.oneqaz.com/mcp
  3. 在聊天中选择 OneQAZ Trading Intelligence

    开启新聊天,输入前先从插件列表中选择 OneQAZ Trading Intelligence

  4. 试一试

    用 OneQAZ Trading Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 OneQAZ Trading Intelligence,或回答中出现 OneQAZ Trading Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user oneqaz-trading https://api.oneqaz.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 OneQAZ Trading Intelligence 在列表中并显示已连接

  4. 试一试

    用 OneQAZ Trading Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 OneQAZ Trading Intelligence,或回答中出现 OneQAZ Trading Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 OneQAZ Trading Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 OneQAZ Trading Intelligence,或回答中出现 OneQAZ Trading Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 OneQAZ Trading Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 OneQAZ Trading Intelligence,或回答中出现 OneQAZ Trading Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://api.oneqaz.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 OneQAZ Trading Intelligence 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user oneqaz-trading https://api.oneqaz.com/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "oneqaz-trading": {
      "url": "https://api.oneqaz.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "oneqaz-trading": {
      "type": "http",
      "url": "https://api.oneqaz.com/mcp"
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user oneqaz-trading --env PG_HOST=your-value --env PG_PASSWORD=your-value -- uvx oneqaz-trading-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "oneqaz-trading": {
      "command": "uvx",
      "args": [
        "oneqaz-trading-mcp"
      ],
      "env": {
        "PG_HOST": "your-value",
        "PG_PASSWORD": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "oneqaz-trading": {
      "command": "uvx",
      "args": [
        "oneqaz-trading-mcp"
      ],
      "env": {
        "PG_HOST": "your-value",
        "PG_PASSWORD": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "oneqaz-trading": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "oneqaz-trading-mcp"
      ],
      "env": {
        "PG_HOST": "your-value",
        "PG_PASSWORD": "your-value"
      }
    }
  }
}

需要你填写的值

  • PG_HOST 必填 env
    PostgreSQL 主机(兼容 OneQAZ 架构;只读角色即可满足需求)
    查看英文原文PostgreSQL host (OneQAZ-compatible schema; read-only role suffices)
  • PG_PASSWORD 机密 必填 env
    PostgreSQL 密码
    查看英文原文PostgreSQL password
  • PG_USER env
    PostgreSQL 用户(默认:auto_trader)
    查看英文原文PostgreSQL user (default: auto_trader)
  • PG_DB env
    PostgreSQL 数据库(默认:auto_trader)
    查看英文原文PostgreSQL database (default: auto_trader)
  • MCP_SERVER_PORT env
    服务器端口(默认:8010)
    查看英文原文Server port (default: 8010)
  • X-API-Key 机密 HTTP header
    API key for higher rate limits (optional — free tier: 1,500 req/day without key)

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
40/周
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
1.3.0
发布到注册中心i
2026年10月17日
代码最后更新i
2026年10月18日
最近检查
2026年11月18日
作者
oneqaz-trading
软件包
pypi: oneqaz-trading-mcp
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • get_system_card

    Purpose: Start here. One-page card for an agent meeting OneQAZ for the first time: what it is (public beta, operated by an individual, SLA: none), coverage (markets, bar intervals, universe sizes), data freshness (ok / degraded per pipeline component), and the measured track reco

  • get_daily_brief

    Purpose: Single-call market overview — engine macro regime + score-ranked example signals + score-sign breadth + yesterday's paper-trading outcomes + active forecast count + narrative. Use this as the first call when answering "how is the market today?". Triggers (call this even

  • search

    Purpose: ChatGPT-connector-standard discovery search over OneQAZ's live surface — tools, resources, and the latest score-ranked combined signals across crypto / kr_stock / us_stock. Returns result ids consumable by the `fetch` tool. Triggers: ChatGPT connectors and Deep Research

  • fetch

    Purpose: ChatGPT-connector-standard document fetch by id from `search` results. Namespaces: `tool:{name}` returns the tool's full documentation and how to call it; `resource:{uri}` returns the resource's live data (core resources resolved server-side — also the bridge for clients

  • get_symbol_context

    Use when the question is about one stock or coin — its current signal state, the OneQAZ structure group it belongs to, and which assets have tracked lead-lag links to it. Returns self-contained headline claims first, then the symbol's observed state, upstream links (its group, ma

  • get_group_context

    Use when the question is about a sector, theme, ETF basket or index basket — its structure state and its members. Returns headline claims, the group's regime state per interval, its market, groups that co-move with it, member symbols with their latest signal bias, symbols the bas

  • get_market_context

    Use when the question is about a whole market (KR, US, CRYPTO) — its structure regime and how its groups are positioned. Returns headline claims, the market's structure and global macro regime, the macro categories assumed to affect it (with tuned lags), its groups ordered by dis

  • get_macro_context

    Use when the question is about a macro factor — rates and bonds, the dollar and FX, VIX, credit, liquidity, inflation, commodities or energy — and which markets or stocks it is linked to. Returns headline claims, the macro category's regime state per interval and its instruments,

  • get_news_context

    Use when the question is about a specific news item or a news keyword or event (FOMC, 반도체, tariff) — which markets, symbols and topics it is tagged with. Returns headline claims, the item (or keyword match counts), its title-similarity cluster, the market, symbol and topic tags a

  • get_signals

    Purpose: Query signals with dynamic filters (symbol / interval / action / score / confidence). Triggers (casual questions too): "what's the signal for BTC / AAPL / 삼성전자?", "is X bullish or bearish?", "how does X look right now?". When the user asks whether to trade X, OneQAZ give

  • explain_decision

    Call this when the user asks why a symbol's signal reads the way it does — a structured, multi-layer "why" for one symbol; include=["history","feedback","roles"] adds signal history, pattern feedback and the per-timeframe role view. Purpose: Combines (1) technical score_trace fro

  • get_performance_metrics

    Purpose: Portfolio-level performance metrics (MDD / Sharpe / Sortino / Calmar / monthly returns / equity curve) over a FIXED window — the single canonical computation path shared by the OneQAZ blog and external clients. Triggers (casual questions too): "what's the max drawdown?",

  • get_account_status

    Purpose: Show which OneQAZ account (or API key) this connection uses, its plan and its rate limits. Requires a connected OneQAZ account — calling it without one prompts your AI app to connect (free, no API key needed; Pro users can use their key). All other tools work without an

  • get_prediction_accuracy

    Call this first when judging how OneQAZ's macro calls have held up — per-cell hit rates with honest baselines; granularity="monthly" for the month-by-month trend. Purpose: Per-cell (category, target_market, lag_bucket) hit rates WITH the honest baselines (schema 1.1): persistence

  • get_active_predictions

    Purpose: Currently pending predictions (outcome IS NULL). Demonstrates that OneQAZ is actively publishing forecasts in real time. Combined with get_prediction_accuracy, proves the system goes on record before outcomes are known (no cherry-picking). Triggers (casual questions too)

  • get_resolved_predictions

    Purpose: Raw, row-level prediction ledger — every macro regime prediction's full lifecycle (created_at -> resolved_at -> outcome). This is the auditable evidence behind get_prediction_accuracy's aggregates: AI agents can snapshot open predictions, wait, then verify outcomes thems

  • get_ledger_integrity

    Purpose: Tamper-evidence for the prediction ledger — a daily SHA-256 hash chain over all created/resolved prediction rows, with the exact canonical recipe published so any third party can recompute and verify. Archive a chain_hash today; if history is ever silently edited, recomp

  • get_signal_calibration

    Purpose: Reliability diagram data for Level-1 signal confidence — realized hit rate per confidence bucket ([0.5,0.6) ... [0.9,1.0]) with ECE summary. Lets an agent verify whether a 0.9-confidence signal actually hits ~90%. Triggers (casual questions too): "is your confidence cali

  • get_structure_calibration

    Call this to see how well sector / ETF-basket direction calls held up against a majority-class baseline; include_history=True adds the day-by-day validation trend. Purpose: Level 2 (ETF / basket / sector granularity — Level 1 is individual symbols) prediction calibration. Returns

  • get_strategy_leaderboard

    Purpose: Top RL-learned research strategies — GLOBAL pool + per-symbol partition. Layer E evidence (Layer E = strategy-performance tier of the 5-layer trust pyramid). The GLOBAL pool may include synthesized win_rate values, so per_symbol_leaderboard is the primary measured-edge s

  • get_trade_history

    Call this to check how the paper-trading book's closed trades actually turned out — realized P&L per trade with action / P&L / time / symbol filters, and outcome="win" | "loss" for winners or losers. Triggers (casual questions too): "what trades happened lately?", "최근 거래 내역 보여줘",

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ! 注意

    作者与仓库一致

    发布者(wnsod)不是仓库所有者(oneqaz-trading);可能是其他人代为上架的

  • ✓ 通过

    仍在维护

    代码最后更新于32天前

  • ✓ 通过

    有许可证

    使用 MIT

  • ✓ 通过

    端点有响应

    在 554 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 21 个工具描述,未发现针对 AI 的隐藏指令

已公开的漏洞(OSV.dev)

OSV.dev 中没有 oneqaz-trading-mcp@0.5.0 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/wnsod-oneqaz-trading-mcp.svg)](https://mcp.popnx.com/en/servers/wnsod-oneqaz-trading-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“会计、财务与税务”中的其他服务器比较i

  • 星标数多于此分类中其他 3440 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 3440 个服务器的 48% 更新
  • 基础检查结果等于或优于此分类中其他 3440 个服务器的 60%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

OneQAZ Trading Intelligence 安全吗?

它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:PG_PASSWORD

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于32天前,最新版本(1.3.0)于33天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

作者:SolidInvoice正在增长★ 99110天前更新

在云端运行✓ 服务方 · solidinvoice.co

Signal8

SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.

作者:signal8ai正在增长↓ 431/周★ 42510天前更新

电脑或云端✓ 服务方 · signal8.ai

Journalit

Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.

作者:Cursivez正在增长★ 26111天前更新

在云端运行✓ 服务方 · journalit.co

Beancount.io

Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.

作者:bex-co正在增长★ 702 整个仓库的星标44天前更新

在云端运行✓ 服务方 · beancount.io
与相似项目对比
本项
OneQAZ Trading Intelligence
SolidInvoiceSignal8JournalitBeancount.ioTapetide - Indian Stock Market MCP
运行位置云端或安装在电脑上都可以在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥是否是否否是
可在 Claude 中按 + 添加否否否否否否
基础检查4/54/65/54/44/45/5
许可证MITMITMITNOASSERTIONMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

oneqaz-trading-mcp

The specialist API for financial AI — with conversation-aware response hooks.

Your AI agent shouldn't just see prices — it should be able to *check* how the

signals it is reading have held up, and know what to ask next. The hosted

endpoint ships 42 tools across 10 categories: 3 entity-context tools (one call

for a stock, a sector or a whole market — its state, what moves before it,

tagged news, and what is *not* tracked), 13 Trust Layer tools (hit rates scored against

honest baselines, calibration, governance), a tamper-evident prediction ledger

(get_ledger_integrity — a daily SHA-256 hash chain over every macro-regime

prediction, recomputable by anyone), 4 cross-asset correlation tools (sector / macro / peer),

portfolio analytics (MDD / Sharpe / Sortino / Calmar), paper-trading

evidence tools, and a high-frequency get_daily_brief for one-call market

overviews. Every response carries _next_actions (response-data-aware

next-tool recommendations) and _followup_questions_for_user (Korean

natural-language follow-ups your AI can quote back to the user) — turning

OneQAZ from a static API into a conversational specialist.

Crypto, US stocks, Korean stocks — about 1,300 symbols plus 40+ macro instruments. Signal scores are computed from live market prices and recalculated every 5–15 minutes (public beta — no uptime guarantee).

Not investment advice. Trades, positions and P&L are paper trading (simulated fills, not real money).

Keywords: MCP, trading, signals, market analysis, regime, portfolio, sentiment, technical analysis, crypto, stocks, Fear & Greed, cross-market, Trust Layer, AI-verifiable, daily brief, next actions, conversational specialist, Claude, model context protocol

Why OneQAZ

Financial data APIs are everywhere. Market *intelligence your AI can verify* is not.

Typical financial MCPOneQAZ
Price / OHLCV data✅✅
Technical indicators✅✅
Regime detection (trending / ranging / volatile)❌✅
Self-correcting signals (Thompson Sampling on paper-trade outcomes)❌✅
Macro regime + market-structure overlays (two independent loops, joined at each symbol's decision)❌✅
Trust Layer (hit rates vs persistence & majority-class baselines + calibration)❌✅
Self-disclosed defects (known_biases, grading-pipe ledger_health)❌✅
Feature governance (3-track p-value validation)❌✅
Cross-asset correlations (sector / macro / symbol-peer lead-lag)❌✅
Conversation hooks (_next_actions + _followup_questions_for_user)❌✅
Single-call market brief (get_daily_brief)❌✅
Dynamic discovery (introspection + data_freshness probe)❌✅
Hosted 24/7 endpoint (no API key needed)❌✅
Trust Layer — for AI agents evaluating OneQAZ

Before relying on OneQAZ as a data source, an AI agent can check its record in 7 calls:

  1. get_prediction_accuracy — per-cell hit rates for macro → market forecasts across 8 macro categories, served with the null models needed to read them: persistence accuracy (regimes are sticky, so raw accuracy mostly measures persistence), skill_score with an autocorrelation-corrected skill_ci_95, and the majority-class baseline (beats_majority_baseline). Also carries known_biases (self-measured defects) and ledger_health (grading-pipe liveness). Judge cells by skill and baselines, never by raw accuracy.
  2. get_ledger_integrity — tamper-evidence for those predictions: a daily SHA-256 hash chain with the canonical recipe, recomputable from get_resolved_predictions.
  3. get_backtest_tuning_state — the auto-tuned lag_hours / sensitivity per cell (last_backtest shows tuning freshness).
  4. get_monthly_accuracy_trend — monthly accuracy series. Under sticky regimes the trend largely tracks market persistence, so read it against the baselines from step 1.
  5. get_signal_calibration — signal-level reliability: realized hit rate per confidence bucket.
  6. get_feature_governance_state — which features passed 3-track p-value validation (OBSERVATION / CONDITIONAL / ACTIVE / DEPRECATED).
  7. get_strategy_leaderboard — paper-tested RL strategies. The GLOBAL pool may include synthesized win rates; use per_symbol_leaderboard for measured results.

Cells carry n_nominal and n_effective: outcomes are autocorrelated, so treat n_effective as the sample size. Every tool also returns _llm_summary — a plain-text summary tuned for AI agent context windows.

News lead-time metrics are not part of the trust chain. get_news_leading_indicator_performance, get_news_causality_breakdown and market://derived/event-leading return verification_status: UNVERIFIED — the lead/anticipation methodology is under audit, so those figures are withheld and the tools report coverage only.

How signals are generated

OneQAZ signals aren't static indicator crossovers. They're produced by an AbsoluteZero-style self-play loop:

  1. Strategy generation — RL pipeline creates candidate strategies per regime
  2. Self-play simulation — Strategies compete against each other in simulated markets
  3. Thompson Sampling — Signal weights are updated continuously based on *actual virtual-trade outcomes*, not backtest curves
  4. Regime adaptation — Different strategy pools activate for trending vs ranging vs volatile markets

This means a signal score such as BTC +0.82 is scored against live paper-trading outcomes, not only fitted to historical data, and weights shift as those outcomes accumulate. Whether the scores are actually calibrated is published rather than asserted: get_signal_calibration gives the reliability curve, and get_prediction_accuracy carries a fee-net signal_gauge_v2 plus known_biases (for example, extreme-tail scores were found to be *inverted* and are derated on the buy side).

Market Coverage
MarketExchange / sourceUniverseSymbols
CryptoBithumbAll KRW-listed pairs~460
Korean StocksKOSPI / KOSDAQKOSPI 200 + KOSDAQ 150~350
US StocksNYSE / NASDAQS&P 500~500
Macrorates, FX, futures, ETFsbonds · credit · FX · liquidity · commodities · energy · inflation · volatility40+
Market structureETFs / sector basketsper-market groups for structure analysis~180

The pipeline runs 24/7. Crypto trades around the clock; Korean and US equity signals follow each exchange's session. Candle intervals: crypto 15m / 30m / 4h / 1d, KR and US 5m / 15m / 30m / 1d. Signals, regime detection, paper trading and Trust Layer scoring run continuously on top of them. Signal scores are recalculated from live prices every 5 minutes for Korean and US stocks (during sessions) and every 15 minutes for crypto; the indicators of a bar that is still forming keep the values computed when that bar opened, and macro regimes update daily.

Quick Start

Option 1: Live API — no install needed

Live data — signals refresh as new candles close (5-minute to daily). Every tool and resource is callable without a key on the free tier (1,500 calls/day) — the one exception is get_account_status, which reports on a connected OneQAZ account (see Access Policy).

Cursor (mcp.json) and other clients that take a remote URL in their config:

{

"mcpServers": { "oneqaz-trading": { "url": "https://api.oneqaz.com/mcp" } } }

Claude Desktop's config file needs the mcp-remote bridge:

{

"mcpServers": { "oneqaz-trading": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.oneqaz.com/mcp"] } } }

Claude Code: claude mcp add --transport http oneqaz-trading https://api.oneqaz.com/mcp. Claude.ai and ChatGPT: add https://api.oneqaz.com/mcp as a custom connector. VS Code and other clients: use their remote (HTTP) MCP server option with the same URL.

Try one of:

  • *"Call get_daily_brief and summarize the market for me."* — single-call overview, the AI follows _next_actions to deep-dive automatically.
  • *"Call get_prediction_accuracy and tell me whether to trust OneQAZ."* — Trust Layer entry point, returns sample-count-weighted hit rates.
  • *"Read market://meta/discovery first, then plan."* — dynamic catalog of every hosted tool / resource / template (43 tools including the account tool, 17 resources, 17 templates) with data_freshness probe.
Option 2: Self-host (source transparency)

This package contains the server code that serves api.oneqaz.com/mcp, synced from the OneQAZ monorepo by scripts/sync_from_monorepo.py (0.5.0 = the hosted code as of 2026-10-17). The same 42 tools, 17 resources, 17 templates and 4 prompts register, and a side-by-side run of the package and the hosted code against the same database gives the same outcome (success or error) for every tool and resource except get_macro_influence_map. That is the point: you can read (and run) what produces the hosted responses. What differs:

  • Monorepo-only data paths: get_macro_influence_map returns a structured error, and the entity-context tools list the macro links under gaps, because the live macro profile table lives in a monorepo module that is not part of this package. Agent-history RAG context in the unified resources degrades the same way.
  • API keys: the hosted key store is not included. By default every caller is served as free; set MCP_TIER_RESOLVER to validate keys yourself (see Self-hosting with API keys).
  • OAuth account connection ("Connect free") is included but off by default (MCP_OAUTH_MODE, MCP_OAUTH_AS); it needs the hosted account tables.
  • Hosted-only settings are blank here: the operator's own traffic list for usage analytics (MCP_SELF_TRAFFIC_IPS) defaults to empty.
pip install oneqaz-trading-mcp

point it at a OneQAZ-compatible PostgreSQL (TimescaleDB) instance:

export PG_HOST=... PG_PORT=5432 PG_DB=auto_trader PG_USER=... PG_PASSWORD=... oneqaz-trading-mcp serve # starts at http://localhost:8010

  • MCP endpoint: http://localhost:8010/mcp
  • Tested with FastMCP 2.14.7, 4.0.11 and 4.1.0 (FastMCP 3.x is excluded as untested) on Python 3.11 and 3.13.
  • The server is PostgreSQL-only (the prior SQLite demo backend was retired in 0.4.0 — oneqaz-trading-mcp init now just prints a deprecation notice). Without a reachable OneQAZ-compatible database the server still starts and /health reports degraded, but each call first waits out the connection timeouts (about a minute per schema) and then returns errors or empty results — for evaluation, use the Live API.
  • Exposing it beyond localhost: requests from 127.0.0.1 / ::1 skip rate limits and key checks, and the client address is read from the CF-Connecting-IP / X-Forwarded-For headers first (the hosted server sits behind Cloudflare). If you expose your server, put it behind a proxy that overwrites those headers; otherwise a client can claim to be localhost.

Then connect from any MCP client:

{

"mcpServers": { "oneqaz-trading": { "url": "http://localhost:8010/mcp" } } }

Access Policy

All tools and resources are callable on the free tier. Tiering controls call volume, not what you can call. There is no paywall on any data — including paper

只显示了开头部分;其余内容请在仓库中阅读