Rule Trade - Japanese equity verification layer
REMOTE · RULETRADE.JP · SCANNED OCT 5
Verified Japanese equity studies: 50 anomalies, 26 indicators, 12 candlesticks, events, ETF decay.
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 → Why this is hard to score →
Endpoint Security63
- 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 8 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2563 tokens (~320/item across 8 items; 8 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Rule Trade - Japanese equity verification layer MCP server?
Rule Trade - Japanese equity verification layer is a hosted endpoint at https://ruletrade.jp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ruletrade.jp
claude mcp add --transport http jp-ruletrade-mcp 'https://ruletrade.jp/mcp'
{
"mcpServers": {
"jp-ruletrade-mcp": {
"url": "https://ruletrade.jp/mcp"
}
}
} {
"servers": {
"jp-ruletrade-mcp": {
"type": "http",
"url": "https://ruletrade.jp/mcp"
}
}
} [mcp_servers.jp-ruletrade-mcp] url = "https://ruletrade.jp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-ruletrade-mcp": {
"type": "remote",
"url": "https://ruletrade.jp/mcp",
"enabled": true
}
}
} openclaw mcp add jp-ruletrade-mcp --url 'https://ruletrade.jp/mcp' --transport streamable-http
mcp_servers:
jp-ruletrade-mcp:
url: "https://ruletrade.jp/mcp" {
"McpServers": {
"jp-ruletrade-mcp": {
"Transport": "http",
"Url": "https://ruletrade.jp/mcp"
}
}
} assistant mcp add jp-ruletrade-mcp -t streamable-http -u 'https://ruletrade.jp/mcp'
{
"mcpServers": {
"jp-ruletrade-mcp": {
"type": "http",
"url": "https://ruletrade.jp/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.
- 5 Oct 26 0
- Stability: 0.97 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Oct 2026 · Probed https://ruletrade.jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ruletrade.jp | CN=YR1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | RSA 2048 | SHA256-RSA | 6b1ba3db06c36e53177a0170cacae6bceaa |
| SANs: ruletrade.jp | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ruletrade.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| ruletrade.jp. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ruletrade.jp/mcp | Verified | 200 | |
| http (plaintext) | http://ruletrade.jp/mcp | HTTPS enforced | 308 | https://ruletrade.jp/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_anomaly_summary アノマリー検証結果(ジンクス50本)+暴落前兆(傾斜計5・着火メーター7) ~341
日本株の言い伝え(アノマリー/ジンクス)50本を61年分の日経平均データで検証した結果(判定・勝率・平均リターン・標本数・p値)を返す。name を渡すとその名前を含むものだけに絞り込める(例: セルインメイ, 節分天井, 干支)。あわせて、5つの暴落前兆(逆イールド・CAPE・信用膨張・過熱・引き締め)の点灯状況と、着火メーター(7フラグ・20営業日以内に-10%が起きた過去の割合)の現在値も返す。detail=true で年代別の内訳・統計表・書籍上の根拠を含める。返すのは判定結果と統計値のみで、価格系列や財務値は含まない。
| Name | Type | Req | Description |
|---|---|---|---|
| detail | boolean | – | 年代別の内訳(extra)・中央値/標準偏差/対照群・書籍上の根拠(book)・着火メーターの統計表と履歴を含めるか |
| name | string | – | アノマリー名またはカテゴリの部分一致で絞り込む(例: セルインメイ / 節分 / 曜日 / 都市伝説)。省略すると全50本の要約を返す |
No output schema declared.
No examples provided.
get_candlestick_verdict 酒田五法12本の検証結果(採用ゼロ本) ~368
三尊天井・赤三兵・三空叩き込みなど酒田五法12本を東証プライム1,550銘柄・10年半で検証した結果を返す。取引回数・勝率・PF・平均超過収益・p値・負け年・5つの採用基準のどれで落ちたか・不採用の理由を含む。12本すべてが採用基準を満たさなかった(採用ゼロ本)。最も PF の高い三空叩き込み(PF 3.04)も、期間を前半と後半に分けると符号が反転するため不採用としている。pattern を渡すとその形だけに絞り込める(日本語・英語の別名可。例: 三尊, head and shoulders, 赤三兵)。detail=true で保有日数別・相場環境別の内訳を含める。銘柄名・銘柄コード・価格は含まない。
| Name | Type | Req | Description |
|---|---|---|---|
| detail | boolean | – | 保有日数別(5/10/20営業日)の内訳・75日移動平均で分けた相場環境別の内訳・検証に使った規定値を含めるか |
| pattern | string | – | 形の名前で絞り込む(部分一致・日英の別名可。例: 三尊 / 逆三尊 / 三空 / 赤三兵 / morning star)。省略すると12本の一覧を返す |
No output schema declared.
No examples provided.
get_daily_signals 公開ルールに該当した銘柄(1件・1営業日遅れ) ~171
公開ルール(BNF 25日線乖離が -15% 以下)に該当した銘柄を返す。★返すのは1件だけ★(該当した全銘柄の一覧は配布しない)。件数は返すので「今日は何件あったか」は分かる。1営業日遅れ(前営業日の終値で判定)。価格・株数・利確/損切ラインは含まない。該当は機械的な条件への一致であって、売買の判断ではない。
| Name | Type | Req | Description |
|---|---|---|---|
| strategy | string | – | ルール名。現在は bnf(25日線乖離の逆張りルール)のみ |
No output schema declared.
No examples provided.
get_etf_decay レバレッジ・インバースETFの減価(12年の実測) ~359
日経ダブルインバース(1357)などレバレッジ・インバース型ETFを12年・2,964営業日ぶん実測した結果を返す。年別の理論値と実績・保有日数別の勝率と理論との乖離・地合い条件別の PF と最大ドローダウン・「戻るまで待つ」を305回試した結果を含む。日々の値動きを2倍にする商品なので、上下を往復するだけで元に戻らない(日経が+10%のあと-9.1%で元の水準に戻る2日間で、100→80→94.5)。検証結果には各節の「解釈で注意すべき点」を必ず添えて返す(日経が12年で約4倍になった上昇相場のデータであるため)。detail=true で地合い条件別の72通りを含める。日足の価格系列と個別株の銘柄情報は含まない。
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | 検証対象のETF(1357=ダブルインバース / 1570=レバレッジ)。省略すると両方を含む全体を返す |
| detail | boolean | – | 地合い条件別(75日線割れ初日・200日線割れ初日など8条件 × 保有日数4 × コスト2 = 72通り)の PF と最大ドローダウンを含めるか |
No output schema declared.
No examples provided.
get_event_reaction 出来事のあとに何が起きたか(3つの検証) ~595
ある出来事のあとに何が起きたかを、3つの検証からまとめて返す。(1)出来事27種 — 地震・利上げ・円安・関税・パンデミックなどのあと、市場全体を上回る動きがあったか。判定は 持続型/初動型/不発/逆行/市場全体のみ の5種類と、5つの窓(当日/翌日/5営業日後/1か月後/3か月後)の超過収益・勝率・p値。(2)決算後のドリフト — 決算発表のあと値動きが続くか。約26,000件の決算で検証。(3)指数の入替 — TOPIX の採用・除外でいつ・どちら向きに動くか。3つは別々のデータから同じ形を示している: 反応は出来事を通過する前か、ごく初期に終わる。出来事27種の「初動型」は翌朝の寄り付きで終わり、決算後のドリフトは+5日で統計的に消え、指数の入替は実施日で止まる。event を渡すと絞り込める(例: 地震, earthquake, 利上げ, 決算, PEAD, TOPIX, 日経225)。省略すると3つの見出しを返す。銘柄名・銘柄コード・銘柄バスケットは含まない。返すのは分類と統計だけ。
| Name | Type | Req | Description |
|---|---|---|---|
| detail | boolean | – | 絞り込んだときに、分類前の全標本数・各窓での市場全体の動き・決算の区分別内訳(発表時刻/四半期/規模/期間)とルール別の成績まで含めるか。event を省略したときは効かない(全件の詳細は 50KB を超えるため) |
| event | string | – | 出来事の名前で絞り込む(部分一致・日英の別名可)。出来事27種: 地震 / earthquake / 利上げ / 円安 / 関税 / パンデミック など。決算後のドリフト: 決算 / earnings / PEAD。指数の入替: TOPIX / 日経225 / 除外 / 採用。省略すると3つの検証の見出しと、出来事27種の一覧を返す |
No output schema declared.
No examples provided.
get_indicator_verdict テクニカル指標26種の検証結果(使える9 / 条件付き4 / 捨てろ13) ~392
RSI・MACD・移動平均クロス・ボリンジャーバンドなどテクニカル指標26種を、教科書どおりの買い方で TOPIX500・10年・約50万回の売買として検証した結果を返す。勝率・期待値・PF・ランダムな売買との超過収益を、出口2種類(20営業日で手仕舞い / 8%トレーリング)で返す。判定は 使える9個 / 条件付き4個 / 捨てろ13個 の3段。「使える」の基準は8区分(出口2 × 上昇/下落/前半/後半)すべてで超過収益が +0.3% を超えること。捨てろ13個には入門書の最初に出てくる指標が並んでいる。name を渡すとその指標だけに絞り込める(日本語・英語の別名可。例: RSI, 一目, ichimoku, 乖離率)。detail=true で8区分すべての内訳を含める。銘柄名・銘柄コード・価格は含まない。
| Name | Type | Req | Description |
|---|---|---|---|
| detail | boolean | – | 8区分(出口A・B × 上昇/下落/前半/後半)それぞれの超過収益を含めるか |
| name | string | – | 指標名またはカテゴリで絞り込む(部分一致・日英の別名可。例: RSI / MACD / ボリンジャー / オシレーター / volume)。省略すると26種の一覧を返す |
No output schema declared.
No examples provided.
get_market_regime 地合い判定(BULLISH/NEUTRAL/BEARISH/PANIC)と3軸スコア ~199
本番システムが日中に更新している相場環境の判定、サーキットブレーカー(HALT)状態、VIX、日経平均、当日シグナル件数を返す。あわせて3軸スコア(トレンド・短期リスク・需給をそれぞれ -2〜+2 で採点し、合計 -6〜+6 を5段階に分けたもの)と、各軸がその点数になった理由・5営業日以内の大型イベントを返す。銘柄名は含まない。オプションで日次履歴も返す。相場の予想ではない。
| Name | Type | Req | Description |
|---|---|---|---|
| history_days | integer | – | 直近N日分の地合い履歴を含める(0=含めない、最大60) |
No output schema declared.
No examples provided.
list_tools_guide 使い方ガイド・データ更新時刻・免責 ~68
このサーバーの全ツール(8本)の説明、データの更新タイミングと遅延、返さないものの一覧、免責事項、今後の予定を返す。最初に一度呼ぶことを想定。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Rule Trade - Japanese equity verification layer MCP server?
Rule Trade - Japanese equity verification layer is an MCP server listed in the public MCP registry as jp.ruletrade/mcp. Verified Japanese equity studies: 50 anomalies, 26 indicators, 12 candlesticks, events, ETF decay. This page covers its hosted endpoint (https://ruletrade.jp/mcp).
Is the Rule Trade - Japanese equity verification layer MCP server safe to use?
Rule Trade - Japanese equity verification layer scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Rule Trade - Japanese equity verification layer MCP server expose?
Rule Trade - Japanese equity verification layer exposes 8 tools: get_daily_signals, get_market_regime, get_anomaly_summary, get_candlestick_verdict, get_event_reaction, and 3 more. Their descriptions and schemas cost roughly 2,493 tokens of context every time the server is loaded.
Does the Rule Trade - Japanese equity verification layer MCP server require authentication?
No. We connected to Rule Trade - Japanese equity verification layer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rule Trade - Japanese equity verification layer MCP server still maintained?
Rule Trade - Japanese equity verification layer is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.