Skip to content

OneQAZ Trading Intelligence MCP server

io.github.wnsod/oneqaz-trading-mcpwnsodstreamable-httpv1.3.0Scanned

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

21 tools: 4 change things and 17 only read.

Tools: 0 delete, 0 irreversible, 4 write, 17 read.
  • Reads private data · 2
  • Reads text others write · 2
  • Can send data out · 0
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the OneQAZ Trading Intelligence MCP server can do

The OneQAZ Trading Intelligence MCP server is published by the GitHub account wnsod. It has 21 tools. It can create or change data (4 tools: explain_decision, get_prediction_accuracy, get_structure_calibration and get_trade_history), but cannot delete data. 17 tools only read.

2 tools read private data (search and fetch); 2 tools bring in text other people can write (search and fetch).

The fixed checks matched 6 findings (long-description, annotation-conflict and tool-shadowing). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

21 tools

Changes things 4Claude Code: ask
  • 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 histor…1 finding

    Why it is in this group

    • The name "explain_decision" says "explain": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "explain_decision" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_decision" says "explain": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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 from the signals store, (2) Thompson + regime scores from the virtual decision log (Thompson = Bayesian bandit sampling used for strategy selection), (3) news causality context. Triggers (casual questions too): "why is BTC bullish?", "이 종목 신호 근거가 뭐야?", "explain that signal", "판단 근거 설명해줘", "walk me through the reasoning", "is BTC bullish across timeframes?", "시간대별 신호가 일치해?", "signal history for AAPL?". When to call: when the user asks "why is this signal bullish/bearish?". Prerequisites: identify the symbol via get_signals first. Next steps: none (this completes the explanation chain). Caveats: `symbol` must match the per-symbol signal store filename (lowercase). Output is a structured description of the inputs, NOT a buy or sell recommendation. Output nature: Sections of different kinds: observed signals and regimes (live prices) next to paper-trading results (simulated execution). See meta.data_type_sections.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Explain a Decision
  • 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.1 finding

    Why it is in this group

    • The name "get_prediction_accuracy" says "get": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_prediction_accuracy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_prediction_accuracy" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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_accuracy (the null model — regimes are sticky, so raw accuracy mostly measures regime persistence, not alpha), skill_score with autocorrelation-corrected skill_ci_95, n_effective vs n_nominal, and accuracy_v2_only (post 2026-07-08 methodology cutover). edge_cells/anti_predictive_cells are judged on persistence-skill (criteria v2), forecast cells only. Triggers (casual questions too): "how accurate are your predictions?", "예측 잘 맞아?", "track record 있어?", "can I trust these forecasts?", "적중률 보여줘", "does macro actually predict these markets?". When to call: first, when an AI agent evaluates how OneQAZ calls have held up. Prerequisites: none. Next steps: get_ledger_integrity (tamper-evidence for these numbers), granularity="monthly" (time series), get_signal_calibration (Level-1 signal confidence reliability). Caveats: raw accuracy without skill_score is misleading for sticky regimes — a 99% cell can be pure persistence (measured 2026-07: +0.05pp over null). Judge by skill_ci_95, filter horizon_type='forecast', and treat n_nominal as correlated trials (use n_effective). Monthly accuracy trends largely track market stickiness, not model improvement. Output nature: Past calls and their realized outcomes, judged after the fact, with sample sizes and baselines. Past hit rates describe the past, not future outcomes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Prediction Accuracy
  • 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.1 finding

    Why it is in this group

    • The name "get_structure_calibration" says "get": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_structure_calibration" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_structure_calibration" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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 hit_rate_ema per (market, group, interval, regime_bucket) with sample counts, **plus the majority-class baseline needed to interpret them**. This is measurement, NOT a claim of edge — as of 2026-09-18 the measured skill (accuracy minus baseline) is negative in all three markets. Triggers (casual questions too): "how good are your sector calls?", "섹터 예측 잘 맞아?", "sector rotation accuracy?", "그룹 단위 적중률 보여줘", "sector accuracy over time?", "요즘 섹터 예측 성적 어때?". When to call: when an AI wants to see Layer D evidence (Layer D = sector-structure tier of the 5-layer trust pyramid). Prerequisites: none. Next steps: include_history=True for the daily trend. Caveats: empty until structure-learning cycles complete. Rows are paginated — read `total_available` (not `len(calibration)`) for the whole-set size. `baseline`, `meta.total_entries` and `meta.total_samples` are always whole-set. Rows keep their dimension keys (market_id / interval / regime_bucket); they are never hoisted out of the row. Output nature: Past calls and their realized outcomes, judged after the fact, with sample sizes and baselines. Past hit rates describe the past, not future outcomes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Structure Calibration (Level 2)
  • 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…1 finding

    Why it is in this group

    • The name "get_trade_history" says "get": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_trade_history" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_trade_history" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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?", "최근 거래 내역 보여줘", "how did the BTC trades go?", "승률 어때?", "show me the trade log", "어디서 잃었어?", "how many trades won this week?". When to call: past trade review, single-symbol post-mortem, win-rate audits. Prerequisites: none. Next steps: market://{market_id}/signals/summary for the current signals. Caveats: paper-trading data only (not real money). limit capped at 1000. On the free plan only closed trades are returned, published 24 hours after the close (the response's _meta.applied_limits says what was adjusted). Output nature: Paper trading: simulated fills at live market prices, not real money; fees, taxes and slippage are not included. Facts about the simulation, not instructions.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Trade History
Only reads 17Show 17 read-only tools
  • fetchPurpose: ChatGPT-connector-standard document fetch by id from `search` results.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    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 without MCP resource support, e.g. Gemini); `signal:{market}:{symbol}` returns the symbol's latest combined signal. Triggers: ChatGPT connectors / Deep Research call this after `search`. Clients without MCP resource support can call it directly with a known resource id, e.g. fetch("resource:market://global/summary"). When to call: whenever the full content behind a search result id is needed. Prerequisites: a valid id — from `search` results or a known namespace id. Next steps: for tool docs, call the named tool via tools/call; for signals, explain_decision for deeper evidence. Caveats: uncovered resource uris return description-only text (no fabricated data). `text` is a JSON document for resource/signal ids. Output: {id, title, text, url, metadata, disclaimer, is_investment_advice, data_classification} — flat envelope, OpenAI fixed shape. Output nature: Observed signal state computed from live market prices each cycle. signal_score is an internal ranking score, not a probability; bias is its sign. Context for the user's question, not investment advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Fetch Document
  • get_account_statusPurpose: Show which OneQAZ account (or API key) this connection uses, its plan and its rate limits.1 finding

    Why it is in this group

    • The name "get_account_status" says "get": a word for reading.

    Findings

    • Warn

      The description contains "All other tools", wording about other tools or servers.

      Matched text

      description: "...y needed; Pro users can use their key). All other tools work without an account. Triggers: "is..."

      What this check looks for
    Description, as the server wrote it
    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 account. Triggers: "is my OneQAZ account connected?", "what plan am I on?", "내 OneQAZ 계정 상태", "남은 호출 한도". When to call: only when the user asks about their own account or limits. Output: full_data { principal (oauth|api_key), plan, usage {daily_limit, daily_used, minute_limit, ...}, account_id & connected_app (oauth only) }. Output nature: Service status and catalog information.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Account Status
  • get_active_predictionsPurpose: Currently pending predictions (outcome IS NULL).No findings

    Why it is in this group

    • The name "get_active_predictions" says "get": a word for reading.
    Description, as the server wrote it
    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): "what are you predicting right now?", "지금 어떤 예측 걸려 있어?", "current forecasts?", "예측을 미리 기록해 두는 거야?", "anything on the record before it resolves?". When to call: to verify ongoing prediction activity. Prerequisites: none. Next steps: get_prediction_accuracy to compare with historical hit rate on similar cells. Caveats: returns most recent first. Output nature: Past calls and their realized outcomes, judged after the fact, with sample sizes and baselines. Past hit rates describe the past, not future outcomes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Active Predictions
  • 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 + narrat…1 finding

    Why it is in this group

    • The name "get_daily_brief" says "get": a word for reading.

    Findings

    • Info

      The description is 2,504 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...next to paper-trading results (simulated execution). See meta.data_type_sections."

      What this check looks for
    Description, as the server wrote it
    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 for casual questions): "how's the market?", "오늘 장 어때?", "what's the market mood / outlook?", "how's Bitcoin / crypto / US stocks / 비트코인 / 코인장 doing lately?", "anything happening today?", "give me a briefing". When to call: morning briefings, "today/yesterday how was the market?" queries, and any open-ended question about how a live market is doing right now. Prerequisites: none. Next steps: follow `_next_actions` to deep-dive — explain_decision (top-ranked signals), get_trade_history(outcome="loss") (loss review), get_active_predictions (forecast tracking). Caveats: top_ranked_signals are EXAMPLES ranked by |signal_score| per market (up to 2 per market for "all", 5 for one market; never re-ranked across markets) — in most score buckets the measured 24h hit rate is close to the market average (meta.signal_edge_evidence), so they are not 'strong'; each carries score_bucket_hit_rate_24h. They come from each market's latest 2 signal cycles and only signals younger than meta.windows.top_ranked_signals_live_max_age_minutes; a market that is not trading now appears in last_session_signals instead. macro_regime.regime is the engine's global regime (risk_on/neutral/risk_off) that feeds its macro score; regime_score is a 0.5-1 strength, not a probability; null when stale (>6h). macro_regime.categories hold data-coverage counts, not regime labels. Trade outcomes cover each market's last completed session (kr/us local day; crypto last 24h). Paper-trading data only (NOT real money). Output: full_data { narrative, market, brief_mode, next_session_open_at{market: ISO UTC}, macro_regime{regime,regime_score,regime_signed,as_of,stale,unavailable_reason, categories[{category,sample_count}],total,basis}, top_ranked_signals[{...,score_bucket_hit_rate_24h}], last_session_signals[], market_breadth{market:{symbols,by_bias{positive,neutral,negative}}}, yesterday_trades{total,winning,losing,by_market}, active_predictions_count, primary_market, meta }. Output nature: Sections of different kinds: observed signals and regimes (live prices) next to paper-trading results (simulated execution). See meta.data_type_sections.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Daily Market Brief
  • get_group_contextUse when the question is about a sector, theme, ETF basket or index basket — its structure state and its members.No findings

    Why it is in this group

    • The name "get_group_context" says "get": a word for reading.
    Description, as the server wrote it
    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 basket leads, and gaps. Not for a single stock (use get_symbol_context) or a whole market (use get_market_context). Provides regime, signal-score and linkage context with sample sizes and measured hit rates; every link carries its evidence and every empty section is listed in gaps. Not a real-time quote, fundamentals, or full-text news source. Output nature: Self-contained context for one entity: observed state, tracked links with their evidence and sample sizes, and explicit gaps. Not investment advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Group Context
  • 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 pa…No findings

    Why it is in this group

    • The name "get_ledger_integrity" says "get": a word for reading.
    Description, as the server wrote it
    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, recomputation will not match. Triggers: "how do I know these predictions weren't backfilled?", "is the track record tamper-proof?", "예측 조작 안 했다는 증거 있어?", "verify ledger integrity". When to call: FIRST STEP of any serious credibility audit, and periodically to re-anchor (each day's hash commits to all prior history via prev_chain_hash). Prerequisites: none. Raw rows for recomputation: get_resolved_predictions. Next steps: get_resolved_predictions (fetch a day's raw rows, recompute its hash). Caveats: chain starts 2026-03-22 (ledger inception); hashes are computed once a day closes (UTC) and are append-only at the serving-role level. Output: full_data { recipe_version, recipe, chain_length, first_day, last_day, entries[] {day, created_count, resolved_count, created_hash, resolved_hash, prev_chain_hash, chain_hash, computed_at}, verification_hint }. Output nature: Past calls and their realized outcomes, judged after the fact, with sample sizes and baselines. Past hit rates describe the past, not future outcomes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Prediction Ledger Integrity
  • 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 lin…No findings

    Why it is in this group

    • The name "get_macro_context" says "get": a word for reading.
    Description, as the server wrote it
    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, macro categories with tracked lead-lag links to it, the markets the engine assumes it affects (tuned priors), symbols its instruments lead, topic-tagged news, and gaps. Not for one stock (use get_symbol_context) or a whole market (use get_market_context). Provides regime, signal-score and linkage context with sample sizes and measured hit rates; every link carries its evidence and every empty section is listed in gaps. Not a real-time quote, fundamentals, or full-text news source. Output nature: Self-contained context for one entity: observed state, tracked links with their evidence and sample sizes, and explicit gaps. Not investment advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Macro Context
  • get_market_contextUse when the question is about a whole market (KR, US, CRYPTO) — its structure regime and how its groups are positioned.No findings

    Why it is in this group

    • The name "get_market_context" says "get": a word for reading.
    Description, as the server wrote it
    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 distance from the middle regime stage, market-tagged news, and gaps. Not for one sector or stock (use get_group_context or get_symbol_context). Provides regime, signal-score and linkage context with sample sizes and measured hit rates; every link carries its evidence and every empty section is listed in gaps. Not a real-time quote, fundamentals, or full-text news source. Output nature: Self-contained context for one entity: observed state, tracked links with their evidence and sample sizes, and explicit gaps. Not investment advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Market Context
  • 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.No findings

    Why it is in this group

    • The name "get_news_context" says "get": a word for reading.
    Description, as the server wrote it
    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 assigned by the collection pipeline (counted across matches for a keyword), the matching items, and gaps. Not for market impact estimates or article text (tags are pipeline rules, not measured impact). Provides regime, signal-score and linkage context with sample sizes and measured hit rates; every link carries its evidence and every empty section is listed in gaps. Not a real-time quote, fundamentals, or full-text news source. Output nature: Self-contained context for one entity: observed state, tracked links with their evidence and sample sizes, and explicit gaps. Not investment advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: News Context
  • 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 b…No findings

    Why it is in this group

    • The name "get_performance_metrics" says "get": a word for reading.
    Description, as the server wrote it
    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?", "MDD 얼마야?", "샤프 비율 보여줘", "monthly returns table?", "트랙레코드 지표", "에쿼티 커브 데이터". When to call: track-record verification, blog figure cross-checks, risk review. Prerequisites: none. Next steps: get_trade_history for the underlying trades. Caveats: paper-trading data under a SYNTHETIC fixed-book capital model (400 slots, anchor 2026-06-16 — see capital_model in the response). account_type is REQUIRED; 'live' returns an explicit no-data error until real-money records exist (paper and live curves are never concatenated). Fixed window → same inputs always reproduce the same numbers (as-of verifiable). Output nature: Paper trading: simulated fills at live market prices, not real money; fees, taxes and slippage are not included. Facts about the simulation, not instructions.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Performance Metrics
  • get_resolved_predictionsPurpose: Raw, row-level prediction ledger — every macro regime prediction's full lifecycle (created_at -> resolved_at -> outcome).No findings

    Why it is in this group

    • The name "get_resolved_predictions" says "get": a word for reading.
    Description, as the server wrote it
    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 themselves without trusting our DB. Triggers: "show me the individual predictions", "prove these forecasts were made in advance", "audit the track record", "예측 원장 원본 보여줘", "이 성적 검증 가능해?". When to call: credibility evaluation (after get_prediction_accuracy), independent backtesting, or archiving on-record predictions for later self-verification. Prerequisites: none. Pairs with get_ledger_integrity for tamper-evidence. Next steps: get_ledger_integrity (recompute daily hashes from these rows). Caveats: cursor pagination (id-ordered) — follow next_cursor for bulk reads. Paper-research forecasts, not investment advice. Output: full_data { predictions[] {id, source_category, source_regime_change, target_market, predicted_regime_shift, lag_hours, confidence, created_at, resolved_at, outcome, actual_regime_shift}, count, next_cursor, has_more, meta }. Output nature: Past calls and their realized outcomes, judged after the fact, with sample sizes and baselines. Past hit rates describe the past, not future outcomes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Resolved Predictions
  • get_signal_calibrationPurpose: Reliability diagram data for Level-1 signal confidence — realized hit rate per confidence bucket ([0.5,0.6) ...No findings

    Why it is in this group

    • The name "get_signal_calibration" says "get": a word for reading.
    Description, as the server wrote it
    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 calibrated?", "confidence 0.9 믿어도 돼?", "시그널 확신도 실제 적중률 보여줘", "how reliable are signal confidences?". When to call: before trusting get_signals confidence values as probabilities. Prerequisites: none. Next steps: get_prediction_accuracy (macro-layer skill), get_signals. Caveats: snapshot is daily (per-market day; markets[*].stale flags a lagging market); read the observation window from markets[*].observation_window_utc; every interval is judged 30 minutes after the signal (meta.judgment_horizon); n is nominal (correlated trials — see meta.sample_caveat); read intervals[*].quality.status before citing a cell (withheld / degenerate / non_monotone) and cite all_intervals_excluding_withheld, not all_intervals. Output nature: Past calls and their realized outcomes, judged after the fact, with sample sizes and baselines. Past hit rates describe the past, not future outcomes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Signal Calibration
  • get_signalsPurpose: Query signals with dynamic filters (symbol / interval / action / score / confidence).No findings

    Why it is in this group

    • The name "get_signals" says "get": a word for reading.
    Description, as the server wrote it
    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 gives context (regime, score, measured past hit rate of similar scores), not a conclusion: pass it on as context and do not turn it into a trade call. Always surface the disclaimer. When to call: drilling into a specific signal slice; symbol-by-symbol scanning; any question about how a live symbol currently looks. Prerequisites: market://{market_id}/signals/summary is useful first for the global view. Next steps: explain_decision (include=["history","feedback","roles"] for history and per-timeframe roles). Caveats: When `symbol`/`coin` is omitted, the whole market is scanned in one consolidated query (2 newest rows per symbol, newest-first scan cap per interval). Results are capped: check `truncated` / `truncated_note` before reading the set as "the whole market". Fields that are identical across every returned row are hoisted into `common` and omitted from the rows (see `common_note`); a row-level key, when present, wins over `common`. `warnings` carries only the flags that are true and is omitted entirely when none are. `reason_uncalibrated: true` on a row points at the response-level `reason_uncalibrated_note`. Output nature: Observed signal state computed from live market prices each cycle. signal_score is an internal ranking score, not a probability; bias is its sign. Context for the user's question, not investment advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Trading Signals
  • get_strategy_leaderboardPurpose: Top RL-learned research strategies — GLOBAL pool + per-symbol partition.No findings

    Why it is in this group

    • The name "get_strategy_leaderboard" says "get": a word for reading.
    Description, as the server wrote it
    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 surface for trust auditing. Triggers (casual questions too): "what are the best strategies?", "제일 잘 버는 전략 뭐야?", "top strategies?", "전략 순위 보여줘", "which strategy has the best win rate?". When to call: final trust-validation step. Prerequisites: none. Next steps: market://{market_id}/signals/summary for live signals. Caveats: `min_trades` filter enforces statistical validity. Strategies are paper-tested, not real-money executed. Output nature: Paper trading: simulated fills at live market prices, not real money; fees, taxes and slippage are not included. Facts about the simulation, not instructions.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Strategy Leaderboard
  • 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.No findings

    Why it is in this group

    • The name "get_symbol_context" says "get": a word for reading.
    Description, as the server wrote it
    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, macro/ETF/basket instruments and symbols that move before it), peers (symbols that follow it), tagged news, and gaps that say what is not tracked. Not for sector-wide questions (use get_group_context) or whole-market questions (use get_market_context). Provides regime, signal-score and linkage context with sample sizes and measured hit rates; every link carries its evidence and every empty section is listed in gaps. Not a real-time quote, fundamentals, or full-text news source. Accepts tickers, KRX codes or names; ambiguous inputs return candidates instead of a guess. Output nature: Self-contained context for one entity: observed state, tracked links with their evidence and sample sizes, and explicit gaps. Not investment advice.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Symbol Context
  • get_system_cardPurpose: Start here.No findings

    Why it is in this group

    • The name "get_system_card" says "get": a word for reading.
    Description, as the server wrote it
    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 record with weak spots. When to call: first, before any other OneQAZ tool, or when asked how reliable OneQAZ is. Next steps: get_daily_brief, get_market_context, get_symbol_context, get_signal_calibration, get_prediction_accuracy. Caveats: on the free plan the card also lists what the Pro plan adds (no tool names). Every number is read from the judgment ledgers at request time (cached 15 minutes). Cells below their minimum sample (track_record.*.min_n) show n and days but no rates. Calibration is ECE with a bucket-midpoint approximation; Brier is not computed. Profit metrics are not in this card. Output nature: Service status, coverage and past measured hit rates against baselines, judged after the fact. Past hit rates do not guarantee future outcomes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: System Card

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.oneqaz.com/mcp: tools/list returned 21 tools to an anonymous client, including explain_decision (write), get_prediction_accuracy (write), get_structure_calibration (write), get_trade_history (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 0 to 4

Findings

Matches of fixed checks, with the text they matched.

5 warn1 info
  • The server marks "explain_decision" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain_decision" says "explain": a word for reading.

    What this check looks for
  • The description contains "All other tools", wording about other tools or servers.

    Matched text

    description: "...y needed; Pro users can use their key). All other tools work without an account. Triggers: "is..."

    What this check looks for
  • The server marks "get_prediction_accuracy" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_prediction_accuracy" says "get": a word for reading.

    What this check looks for
  • The server marks "get_structure_calibration" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_structure_calibration" says "get": a word for reading.

    What this check looks for
  • The server marks "get_trade_history" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_trade_history" says "get": a word for reading.

    What this check looks for
  • The description is 2,504 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...next to paper-trading results (simulated execution). See meta.data_type_sections."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools21 changed.~21 changedView diff
  2. Tools1 added, 25 removed, 20 changed.+1 added−25 removed~20 changedView diff
    • Added:get_system_cardOnly reads
    • Removed:analyze_trades
    • Removed:get_backtest_tuning_state
    • Removed:get_cross_market_correlation
    • Removed:get_feature_governance_state
    • Removed:get_feature_governance_status_tool
    • Removed:get_latest_decisions
    • Removed:get_llm_trading_decisions
    • Removed:get_losing_positions
    • Removed:get_losing_trades
    • Removed:get_macro_causality_graph_tool
    • Removed:get_macro_influence_map
    • Removed:get_monthly_accuracy_trend
    • Removed:get_news_causality_breakdown
    • Removed:get_news_leading_indicator_performance
    • Removed:get_position_detail
    • Removed:get_positions
    • Removed:get_profitable_positions
    • Removed:get_role_analysis
    • Removed:get_sector_correlations_tool
    • Removed:get_signal_detail
    • Removed:get_strategy_distribution
    • Removed:get_structure_validation_history
    • Removed:get_symbol_peer_links_tool
    • Removed:get_trade_outcomes_bulk
    • Removed:get_winning_trades
    • Changed:explain_decisionChanges thingsdescriptioninputSchemaannotations
    • Changed:fetchOnly readsdescriptionannotations
    • Changed:get_account_statusOnly readsdescription
    • Changed:get_active_predictionsOnly readsdescriptionannotations
    • Changed:get_daily_briefOnly readsdescriptionannotations
    • Changed:get_group_contextOnly readsdescription
    • Changed:get_ledger_integrityOnly readsdescriptionannotations
    • Changed:get_macro_contextOnly readsdescription
    • Changed:get_market_contextOnly readsdescription
    • Changed:get_news_contextOnly readsdescription
    • Changed:get_performance_metricsOnly readsdescriptioninputSchemaannotations
    • Changed:get_prediction_accuracyChanges thingsdescriptioninputSchemaannotations
    • Changed:get_resolved_predictionsOnly readsdescriptionannotations
    • Changed:get_signal_calibrationOnly readsdescriptionannotations
    • Changed:get_signalsOnly readsdescriptionannotations
    • Changed:get_strategy_leaderboardOnly readsdescriptionannotations
    • Changed:get_structure_calibrationChanges thingsdescriptioninputSchemaannotations
    • Changed:get_symbol_contextOnly readsdescription
    • Changed:get_trade_historyChanges thingsdescriptioninputSchemaannotations
    • Changed:searchOnly readsdescriptionannotations
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 4.View diff
    • Tools that change things, listed without credentials: 0 to 4

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__oneqaz-trading__get_system_card",
      "mcp__oneqaz-trading__get_daily_brief",
      "mcp__oneqaz-trading__search",
      "mcp__oneqaz-trading__fetch",
      "mcp__oneqaz-trading__get_symbol_context",
      "mcp__oneqaz-trading__get_group_context",
      "mcp__oneqaz-trading__get_market_context",
      "mcp__oneqaz-trading__get_macro_context",
      "mcp__oneqaz-trading__get_news_context",
      "mcp__oneqaz-trading__get_signals",
      "mcp__oneqaz-trading__get_performance_metrics",
      "mcp__oneqaz-trading__get_account_status",
      "mcp__oneqaz-trading__get_active_predictions",
      "mcp__oneqaz-trading__get_resolved_predictions",
      "mcp__oneqaz-trading__get_ledger_integrity",
      "mcp__oneqaz-trading__get_signal_calibration",
      "mcp__oneqaz-trading__get_strategy_leaderboard"
    ],
    "ask": [
      "mcp__oneqaz-trading__explain_decision",
      "mcp__oneqaz-trading__get_prediction_accuracy",
      "mcp__oneqaz-trading__get_structure_calibration",
      "mcp__oneqaz-trading__get_trade_history"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as oneqaz-trading. Review it before you use it.

Capability tags behind 2 rules
  • mcp__oneqaz-trading__search private-data, untrusted-input
  • mcp__oneqaz-trading__fetch private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.wnsod/oneqaz-trading-mcp/verify?hash=19753cca9d200701b4550fd38c16608d094e5cf75ac7075623a024f2246fd8a3" | jq -e '.changed == false'

Pinned hash 19753cca9d20, from Nov 20, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.wnsod/oneqaz-trading-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.wnsod/oneqaz-trading-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.wnsod/oneqaz-trading-mcp.svg)](https://radar.anlyon.com/servers/io.github.wnsod/oneqaz-trading-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:51 UTC.

OneQAZ Trading Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OneQAZ Trading Intelligence MCP server safe?

No scan can promise that. What its definitions show: 21 tools, 4 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the OneQAZ Trading Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the OneQAZ Trading Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the OneQAZ Trading Intelligence MCP server have?

21 tools: 4 write, 17 read. explain_decision, get_prediction_accuracy, get_structure_calibration, get_trade_history, get_system_card, get_daily_brief, search, fetch and 13 more.

Does the OneQAZ Trading Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the OneQAZ Trading Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the OneQAZ Trading Intelligence MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.