SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Verifiable crypto/KR/US market intelligence for AI agents: signals, hash-chained ledger. Not advice.
一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり
| 人気 | 0/80 | GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます |
|---|---|---|
| 新しさ | 7/12 | 30 日以内のリリースかコード更新で満点 |
| 応答中 | 8/8 | 前回の確認でクラウドのエンドポイントが応答 |
| 利用スコア | 15/100 |
品質: 基本チェック 4/5 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)
使っているAIアプリを選んで、設定をコピーしてください。
ひとことで AI にインストールしてもらう
OneQAZ Trading Intelligence をインストールして。https://mcp.popnx.com/i/wnsod-oneqaz-trading-mcp.md に従い、コマンドを見せて、私が OK するまで実行しないで。パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · AI が読む全文を見る
チェック 4/5 合格 · 質問内容は提供元のサーバー(api.oneqaz.com)を通ります · ✓ コマンド確認済み 2026年11月14日
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 2 分
キー不要、インストール不要 · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
OneQAZ Trading Intelligencehttps://api.oneqaz.com/mcpClaude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します
+ConnectorsOneQAZ Trading Intelligence
OneQAZ Trading Intelligence を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が OneQAZ Trading Intelligence を使っていると言うか、回答に OneQAZ Trading Intelligence のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT との接続はプランしだい
フル MCP:Web 版 ChatGPT の Business・Enterprise・Edu · Pro:読み取り/取得の権限で接続、データを変えるツールは使えないことがあります · Plus:公式ドキュメントで未確認。プラグイン画面にカスタム MCP を追加する項目があれば試せます · Web のみ
Plugins+Add custom MCP server
名前を入れ、Connection にアドレスを貼り付け、注意事項にチェックして Create as a plugin を押します
OneQAZ Trading Intelligencehttps://api.oneqaz.com/mcp新しいチャットを開き、入力前にプラグインの一覧から OneQAZ Trading Intelligence を選びます
OneQAZ Trading Intelligence を使って、私に何ができるか教えて、1 つやってみせて✓ ChatGPT が OneQAZ Trading Intelligence を使っていると言うか、回答に OneQAZ Trading Intelligence のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に OpenAI のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Claude Code につなげます · 約 2 分
キー不要、インストール不要
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user oneqaz-trading https://api.oneqaz.com/mcpOneQAZ Trading Intelligence が一覧にあり、接続済みと表示されれば OK です
OneQAZ Trading Intelligence を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が OneQAZ Trading Intelligence を使っていると言うか、回答に OneQAZ Trading Intelligence のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 2 分
キー不要、インストール不要
OneQAZ Trading Intelligence を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が OneQAZ Trading Intelligence を使っていると言うか、回答に OneQAZ Trading Intelligence のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 2 分
キー不要、インストール不要
OneQAZ Trading Intelligence を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が OneQAZ Trading Intelligence を使っていると言うか、回答に OneQAZ Trading Intelligence のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください
Web 経由でつなぐアプリ用のアドレス
https://api.oneqaz.com/mcpJSON 設定は下の「開発者向け」にあります
Claude Code
claude mcp add --transport http --scope user oneqaz-trading https://api.oneqaz.com/mcpCursor (~/.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-mcpClaude 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 必須 envPG_PASSWORD 秘密 必須 envPG_USER envPG_DB envMCP_SERVER_PORT env説明は自動翻訳です。変数名は原文のままです。迷ったら原文を確認してください。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
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_cardPurpose: 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_briefPurpose: 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
searchPurpose: 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
fetchPurpose: 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_contextUse 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_contextUse 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_contextUse 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_contextUse 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_contextUse 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_signalsPurpose: 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_decisionCall 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_metricsPurpose: 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_statusPurpose: 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_accuracyCall 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_predictionsPurpose: 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_predictionsPurpose: 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_integrityPurpose: 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_calibrationPurpose: 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_calibrationCall 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_leaderboardPurpose: 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_historyCall 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?", "최근 거래 내역 보여줘",
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月19日にチェック
公開者(wnsod)がリポジトリの所有者(oneqaz-trading)ではありません。別の人が登録した可能性があります
コードの最終更新:32 日前
MITを使用
554ミリ秒で応答(HTTP 200)
サインイン不要
21件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
OSV.dev に oneqaz-trading-mcp@0.5.0 の登録はありません
このバージョンのパッケージ本体のみ確認。すべての依存関係ではありません · 確認日 2026年11月15日
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/wnsod-oneqaz-trading-mcp)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック5項目のうち4項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:PG_PASSWORD
どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。
GitHubリポジトリの最終更新は32 日前、最新バージョン(1.3.0)がレジストリに届いたのは33 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.
Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
48 tools for ~8,000 NSE & BSE stocks: quotes, screener, financials, filings, FII/DII, options
| これ OneQAZ Trading Intelligence | SolidInvoice | Signal8 | Journalit | Beancount.io | Tapetide - Indian Stock Market MCP | |
|---|---|---|---|---|---|---|
| 動く場所 | クラウドでもパソコンにインストールでも使える | クラウドで動き、インストール不要 | クラウドでもパソコンにインストールでも使える | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドでもパソコンにインストールでも使える |
| キーが必要 | はい | いいえ | はい | いいえ | いいえ | はい |
| Claude で + から追加 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| 基本チェック | 4/5 | 4/6 | 5/5 | 4/4 | 4/4 | 5/5 |
| ライセンス | MIT | MIT | MIT | NOASSERTION | MIT | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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_brieffor 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
Financial data APIs are everywhere. Market *intelligence your AI can verify* is not.
| Typical financial MCP | OneQAZ | |
|---|---|---|
| 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) | ❌ | ✅ |
Before relying on OneQAZ as a data source, an AI agent can check its record in 7 calls:
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.get_ledger_integrity — tamper-evidence for those predictions: a daily SHA-256 hash chain with the canonical recipe, recomputable from get_resolved_predictions.get_backtest_tuning_state — the auto-tuned lag_hours / sensitivity per cell (last_backtest shows tuning freshness).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.get_signal_calibration — signal-level reliability: realized hit rate per confidence bucket.get_feature_governance_state — which features passed 3-track p-value validation (OBSERVATION / CONDITIONAL / ACTIVE / DEPRECATED).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_breakdownandmarket://derived/event-leadingreturnverification_status: UNVERIFIED— the lead/anticipation methodology is under audit, so those figures are withheld and the tools report coverage only.
OneQAZ signals aren't static indicator crossovers. They're produced by an AbsoluteZero-style self-play loop:
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 | Exchange / source | Universe | Symbols |
|---|---|---|---|
| Crypto | Bithumb | All KRW-listed pairs | ~460 |
| Korean Stocks | KOSPI / KOSDAQ | KOSPI 200 + KOSDAQ 150 | ~350 |
| US Stocks | NYSE / NASDAQ | S&P 500 | ~500 |
| Macro | rates, FX, futures, ETFs | bonds · credit · FX · liquidity · commodities · energy · inflation · volatility | 40+ |
| Market structure | ETFs / sector baskets | per-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.
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:
get_daily_brief and summarize the market for me."* — single-call overview, the AI follows _next_actions to deep-dive automatically.get_prediction_accuracy and tell me whether to trust OneQAZ."* — Trust Layer entry point, returns sample-count-weighted hit rates.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.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:
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.MCP_TIER_RESOLVER to validate keys yourself (see Self-hosting with API keys).MCP_OAUTH_MODE, MCP_OAUTH_AS); it needs the hosted account tables.MCP_SELF_TRAFFIC_IPS) defaults to empty.pip install oneqaz-trading-mcp
export PG_HOST=... PG_PORT=5432 PG_DB=auto_trader PG_USER=... PG_PASSWORD=... oneqaz-trading-mcp serve # starts at http://localhost:8010
http://localhost:8010/mcponeqaz-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.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" } } }
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