OneQAZ Trading Intelligence
REMOTE · API.ONEQAZ.COM · 2 COMPONENTS · SCANNED AUG 3
Live market data, signals, positions, and macro analysis for crypto, KR stocks, and US stocks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 39 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 13357 tokens (~238/item across 56 items; 39 tools + 17 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.oneqaz.com
claude mcp add --transport http wnsod-oneqaz-trading-mcp https://api.oneqaz.com/mcp
[mcp_servers.wnsod-oneqaz-trading-mcp] url = "https://api.oneqaz.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wnsod-oneqaz-trading-mcp": {
"type": "remote",
"url": "https://api.oneqaz.com/mcp",
"enabled": true
}
}
} openclaw mcp add wnsod-oneqaz-trading-mcp --url https://api.oneqaz.com/mcp --transport streamable-http
mcp_servers:
wnsod-oneqaz-trading-mcp:
url: "https://api.oneqaz.com/mcp" {
"mcpServers": {
"wnsod-oneqaz-trading-mcp": {
"type": "http",
"url": "https://api.oneqaz.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 −4
- HTTPS: pass → unverified ▼ security
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.oneqaz.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oneqaz.com | CN=YE2,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 59ec6adeb737f41dcd096c49eec2997baa5 |
| SANs: *.oneqaz.com, oneqaz.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of api.oneqaz.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oneqaz.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.oneqaz.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.oneqaz.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_trade_history ~324
Purpose: Query paper-trading history with dynamic filters (action / P&L / time / symbol). 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: analyze_trades, market://{market_id}/signals/feedback. Caveats: paper-trading data only (not real money). limit capped at 1000. Args: market_id: Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted) limit: Max results (default 1000) action_filter: Filter by action (all, buy, sell) min_pnl: Min P&L % filter (e.g., -5.0) max_pnl: Max P&L % filter (e.g., 10.0) hours_back: Only trades within last N hours symbol: Filter by ticker symbol (e.g., "BTC", "AAPL"); case-insensitive Disclaimer: Information only, not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| action_filter | string | — | — |
| hours_back | — | — | — |
| limit | integer | — | — |
| market_id | string | yes | — |
| max_pnl | — | — | — |
| min_pnl | — | — | — |
| symbol | — | — | — |
| Name | Type | Req | Description |
|---|---|---|---|
| _followup_questions_for_user | — | — | — |
| _llm_summary | — | — | — |
| _market_state_narrative | — | — | — |
| _next_actions | — | — | — |
| _value_signals | — | — | — |
| action | — | — | Recommended client action (error path) |
| action_value | — | — | — |
| ai_summary | — | — | One-line AI-oriented summary (success path) |
| ai_summary_generated_at | — | — | RFC3339 UTC |
| ai_summary_ttl_seconds | — | — | — |
| data_classification | — | — | — |
| disclaimer | string | yes | Canonical compliance disclaimer (always present) |
| error | — | — | Set true on error responses |
| error_code | — | — | Stable error identifier; see mcp_error_policy.md |
| fallback_note | — | — | — |
| fallback_tool | — | — | Suggested fallback (error path) |
| full_data | — | — | — |
| is_investment_advice | — | — | — |
| is_real_money | — | — | — |
| reason | — | — | Human-readable cause (error path) |
| request_id | string | yes | 32-hex per-response correlation id |
| retryable | — | — | Whether the client should retry (error path) |
| summary_for_user | — | — | One-line jargon-free Korean summary (success path) |
| timestamp | string | yes | RFC3339 UTC, server build time |
No examples provided.
get_trade_outcomes_bulk ~391
Purpose: Cursor-paginated bulk export of the prediction -> trade -> outcome chain — paper trades with realized P&L, each linked (best-effort, same-symbol 2h window) to the signal prediction that preceded entry. Built for pipeline consumers who need offline backtesting data, not conversational snippets. Triggers: "give me your full trade history for backtesting", "bulk export trades", "예측이 실제 매매 성과로 이어졌는지 원데이터로 검증하고 싶다", "download outcomes". When to call: offline verification, periodic ingestion into a research pipeline, or auditing whether signals translate into realized outcomes. Prerequisites: none. For the prediction ledger itself use get_resolved_predictions. Next steps: follow next_cursor until has_more=false; get_resolved_predictions to cross-check linked predictions against the tamper-evident ledger. Caveats: linkage is temporal matching, NOT a foreign key (see meta.linkage). Paper trading only — envelope carries the standard disclaimer once per page. Output: full_data { market, trades[] {id, symbol, action, entry/exit price+ts, profit_loss_pct, holding_duration, entry_signal_score, regime fields, policy_version, sizing fields, linked_prediction{...}|null}, count, linked_prediction_count, next_cursor, has_more, meta }. Args: market: "crypto" (default) / "kr_stock" / "us_stock" cursor: last trade id from previous page (0 = start) limit: page size (max 500) days: exit-time window in days (max 120) Disclaimer: Information only, not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | — | — |
| days | integer | — | — |
| limit | integer | — | — |
| market | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_winning_trades ~172
Purpose: Winning paper trades only (P&L > 0). Convenience wrapper around get_trade_history(min_pnl=0.01). Triggers (casual questions too): "what worked?", "뭐가 제일 잘 벌었어?", "show me the winners", "best trades lately?", "수익 난 거래 보여줘". When to call: success-pattern review. Prerequisites: none. Next steps: analyze_trades for breakdowns. Caveats: paper-trading data only. Args: market_id: Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted) limit: Max results (default 10) Disclaimer: Information only, not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| market_id | string | yes | — |
| Name | Type | Req | Description |
|---|---|---|---|
| _followup_questions_for_user | — | — | — |
| _llm_summary | — | — | — |
| _market_state_narrative | — | — | — |
| _next_actions | — | — | — |
| _value_signals | — | — | — |
| action | — | — | Recommended client action (error path) |
| action_value | — | — | — |
| ai_summary | — | — | One-line AI-oriented summary (success path) |
| ai_summary_generated_at | — | — | RFC3339 UTC |
| ai_summary_ttl_seconds | — | — | — |
| data_classification | — | — | — |
| disclaimer | string | yes | Canonical compliance disclaimer (always present) |
| error | — | — | Set true on error responses |
| error_code | — | — | Stable error identifier; see mcp_error_policy.md |
| fallback_note | — | — | — |
| fallback_tool | — | — | Suggested fallback (error path) |
| full_data | — | — | — |
| is_investment_advice | — | — | — |
| is_real_money | — | — | — |
| reason | — | — | Human-readable cause (error path) |
| request_id | string | yes | 32-hex per-response correlation id |
| retryable | — | — | Whether the client should retry (error path) |
| summary_for_user | — | — | One-line jargon-free Korean summary (success path) |
| timestamp | string | yes | RFC3339 UTC, server build time |
No examples provided.
search ~269
Purpose: ChatGPT-connector-standard discovery search over OneQAZ's live surface — tools, resources, and the latest strong combined signals across crypto / kr_stock / us_stock. Returns result ids consumable by the `fetch` tool. Triggers: ChatGPT connectors and Deep Research call this automatically for any user query routed to OneQAZ ("bitcoin signal", "prediction accuracy", "korean stocks today", ...). Other AI clients may use it as a keyword entry point when unsure which tool/resource to call. When to call: first step of connector-style discovery. MCP-native clients can instead browse tools/list + resources/list directly. Prerequisites: none. Next steps: pass any result id to `fetch` for the full document. Caveats: corpus is rebuilt at most every 10 minutes (tool/resource catalog + top-20 strong signals per market). Empty results list means no match. Output: {results: [{id, title, url}], disclaimer, is_investment_advice, data_classification} — flat envelope, OpenAI fixed shape. Args: query: free-text search string (English/Korean, symbols like BTC/AAPL) Disclaimer: Information only, not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.