Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Rule Trade - Japanese equity verification layer

by oo12takemaru-createversion 0.2.0i★ –iRuns in the cloud
Registry namejp.ruletrade/mcp

Install

Overview

Description from the maker (original English)

Verified Japanese equity studies: 50 anomalies, 26 indicators, 12 candlesticks, events, ETF decay.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 0 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://ruletrade.jp/mcp

Run this in your terminal

claude mcp add --transport http ruletrade https://ruletrade.jp/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ruletrade": {
      "url": "https://ruletrade.jp/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ruletrade": {
      "type": "http",
      "url": "https://ruletrade.jp/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://ruletrade.jp/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ! Caution

    Maker matches the repo

    The publisher (ruletrade.jp) is not the repo owner (oo12takemaru-create); someone else may have listed it

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32706 servers in this category
  • Published to the registry more recently than 44% of the other 32706 servers in this category
  • Basic checks equal to or better than 28% of the other 32706 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Rule Trade - Japanese equity verification layer safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Kanal Varna — drains, leaks & plumbing (Varna, BG)

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Rule Trade MCP / ルールトレード MCP

Endpoint: `https://ruletrade.jp/mcp` (llms.txt: https://ruletrade.jp/mcp/llms.txt · OpenAPI: https://ruletrade.jp/mcp/openapi.json · health: https://ruletrade.jp/mcp/health)

English

A verification layer for Japanese equities, exposed over MCP.

Most Japanese-equity MCP servers cover the *primary data* layer — filings, prices, order execution. This one covers what is missing: what actually happened when published, mechanical rules were applied. It holds no engine of its own; it reads JSON that an existing pipeline publishes daily and reshapes it. Zero dependencies, no API key, no registration.

What you can get
ToolReturns
get_daily_signalsOne stock that matched a published mean-reversion rule (25-day moving-average deviation ≤ -15%), delayed one trading day. Counts are returned; the full list of matches is not distributed.
get_market_regimeMachine-classified market regime (BULLISH / NEUTRAL / BEARISH / PANIC), circuit-breaker state, VIX, Nikkei 225, daily history, and a three-axis score (trend, short-term risk, supply and demand) with the reasoning behind each axis. No stock names.
get_anomaly_summary50 Japanese market anomalies tested over 61 years — verdict, win rate, mean return, sample size, p-value, control group. Filter by name. Plus five crash-precursor gauges and a 7-flag ignition meter verified over 26 years.
get_candlestick_verdictAll 12 classic Japanese candlestick patterns tested on 1,550 TSE Prime stocks over 10.5 years — trades, win rate, profit factor, excess return, p-value, losing years, and which of the five adoption criteria each one failed. None of them cleared the bar. The one with the highest profit factor (3.04) flipped sign between the first and second halves of the sample.
get_event_reactionWhat followed an event, from three separate studies — 27 event types (earthquakes, rate decisions, tariffs, pandemics), post-earnings drift across ~26,000 announcements, and index additions and deletions. All three point the same way: the move happens before the event clears. Per-stock rows and sector baskets are deliberately excluded.
get_indicator_verdict26 technical indicators traded exactly as the textbooks describe — TOPIX500, 10 years, ~500,000 trades. Win rate, expectancy, profit factor and excess return over random entry, across two exits. Nine cleared every regime; thirteen did not, and those thirteen are mostly the ones beginners learn first.
get_etf_decayTwelve years of measured decay in leveraged and inverse ETFs — yearly theory against actual, win rate by holding period, profit factor by market condition, and 305 attempts to hold and wait for a position to come back (99.3% came back; the ones that did not lost 32.5%).
list_tools_guideUpdate times (JST), delays, what is deliberately not returned, disclaimer, roadmap. Call this first.
What you cannot get — by design
  • Raw price series, OHLCV, or financial-statement values
  • Position sizing, entry/exit prices, stop-loss or take-profit levels
  • The production thresholds used by the operator's own system
  • Any recommendation, rating, or buy/sell signal

Every response carries a disclaimer key. Do not strip it when relaying results to a user. Output describes whether mechanical rules matched. It is not investment advice, not a solicitation, and promises no future return.

How to connect
# Claude Code

claude mcp add --transport http ruletrade https://ruletrade.jp/mcp

  • claude.ai: Settings → Connectors → Add custom connector → https://ruletrade.jp/mcp
  • Any MCP client: POST JSON-RPC 2.0 to https://ruletrade.jp/mcp (Streamable HTTP, stateless)
Where the research comes from

The rules and verification data are published as books by the operator (Japanese, Kindle): *Silent Investor BNF*, *Crashes Decay*, and *All 50 Japanese Market Anomalies Tested Over 61 Years*. The anomaly dataset is a fixed snapshot taken at that book's publication (2026-08) and is not updated daily.

Good to know
  • Data updates on Japan Exchange trading days. Exact times are in list_tools_guide.
  • Rate limits are not enforced today. Please be reasonable.
  • Statistical values are rounded; p-values use 3 significant figures so very small values stay readable.

日本語

kaburadar.jp / ruletrade.jp が毎日公開している検証済みJSON(docs/*.json)を、 AIエージェント(Claude / Cursor / ChatGPT 等)から MCP で読めるようにする 変換層 です。 エンジンは持たず、GitHub raw の JSON を読んで整形するだけ。依存パッケージゼロ。

正規URL は `https://ruletrade.jp/mcp`。実体は Cloudflare Workers だが、 ruletrade.jp(Vercel)の vercel.json で rewrite しているため、配信先が変わっても利用者側の URL は変わらない。

ツール読むJSON内容
get_daily_signalsfree_scanner.jsonBNF 25日線乖離ルールの該当銘柄(1営業日遅れ)。返すのは1件のみ・件数は返す
get_market_regimeradar.json / market_jiai.json / radar_history.json / score3.json地合い BULLISH〜PANIC・HALT・VIX・日経・履歴 ＋ 3軸スコア(トレンド/短期リスク/需給・5段階・軸ごとの根拠)
get_anomaly_summaryanomaly_results.json / gauge.json / crash.jsonジンクス50本の検証結果(61年・判定/勝率/p値。name で絞り込み)+ 『暴落は、減衰する』5つの前兆 + 着火メーター(26年検証)
get_candlestick_verdictcandlestick_verdict.json酒田五法12本の検証結果(東証プライム・10年半)。12本すべて不採用・落ちた基準・不採用の理由。pattern で絞り込み(日英の別名可)
get_event_reactionevent_reaction.json / earnings_drift.json / supply_demand_events.json出来事のあとに何が起きたかを3つの検証から。①出来事27種(地震・利上げ・関税ほか) ②決算後のドリフト ③指数の入替。event で絞り込み(地震 / 決算 / TOPIX など)
get_indicator_verdictindicator_verdict.jsonテクニカル指標26種の検証結果(TOPIX500・10年・約50万回)。使える9 / 条件付き4 / 捨てろ13・8区分のどこで基準に届かなかったか。name で絞り込み(日英の別名可)
get_etf_decayetf_decay.jsonレバレッジ・インバースETFの減価(12年の実測)。年別・保有日数別・条件別と「戻るまで待つ」305回の結果。各節の「解釈で注意すべき点」を必ず添える
list_tools_guide(静的)使い方・更新時刻・遅延・免責・今後の予定

法務線は人向けサイトと同一:

  • 銘柄を返すのは1件だけ(2026-09-17 に上位3件から縮小)。該当した全銘柄の一覧は配布しない。件数は返す
  • 推奨語(推奨/おすすめ/買うべき/儲かる 等 src/legal.js の NG_WORDS)は出力から伏せ字にする
  • 全レスポンスに disclaimer キーを常設
  • 価格・株数・利確/損切ライン・本番の調整済み閾値は出さない(free_scanner.json 生成時点で既に落ちている)
  • ジンクス検証は判定結果と統計値(勝率・平均・標本数・p値)のみ。格言の本文(saying)は推奨語を含むため出力しない
  • 書籍の検証も統計値のみ。銘柄名・銘柄コード・銘柄バスケットは返さない。元データに併存する明細(連想の baskets.csv 499行・決算の events_raw.csv・自社株買いの buyback_*.csv 5,523行)は生成側でも開いていない
  • 書籍から取り込む文章は mcp/tools/legal_check.py が JSON を書き出す前に検査する。伏せ字(scrub)は最後の砦で、そこに頼ると「各［表現調整］点の日経平均」のように文の意味が壊れる
  • ETFのコード(1357 等)だけは返す。何を検証したかを示す識別子で、個別株を名指しするのとは別

データの出どころ

docs/*.json は既存の生成側(Python)が毎日書き出しているもの。MCP は読むだけで、生成側は一切触らない。

docs/anomaly_results.json / docs/candlestick_verdict.json / docs/event_reaction.json / docs/indicator_verdict.json / docs/etf_decay.json / docs/earnings_drift.json / docs/supply_demand_events.json の7つは 日次ではなく 書籍刊行時点の固定データ。後の2つは mcp/tools/build_*.py で検証の生出力から機械変換し、 mcp/tools/verify_*.py で元CSVと1つずつ突き合わせている(手で書き写さない)。

docs/anomaly_results.json だけは日次ではなく 書籍刊行時点(2026-08)の固定データ。 元は 株式投資開発/jinx_verification/results/results.json(このリポジトリの外)で、 JSON 非対応の NaN を null に置換したコピー。更新するときは同じ手順でコピーし直す。

エンドポイント

パス内容
POST /mcpMCP Streamable HTTP(JSON-RPC・ステートレス)
GET /health5つのJSONが読めるか確認
GET /llms.txtエージェント向けの説明(英語主・日本語従)
GET /openapi.jsonOpenAPI 3.1。JSON-RPC を1エンドポイントとして記述
GET /概要

デプロイ(どちらか一方でOK・スマホのブラウザから完結)

A. Cloudflare Workers(推奨: ログ保持が長い・無料枠 10万req/日)
  1. Cloudflare ダッシュボード → Workers & Pages → Create → Import a repository
  2. リポジトリ stock-trading- を選ぶ → Root directory に mcp を入れる
  3. Build command は空、Deploy command は npx wrangler deploy(既定のまま)
  4. Deploy → Worker の実体は https://ruletrade-mcp. .workers.dev/mcp。 利用者に案内するのは正規URL `https://ruletrade.jp/mcp`(ruletrade.jp の site/vercel.json が rewrite する)。 Worker の URL が変わったときは site/vercel.json の2行と src/tools.js の CANONICAL_* を直す
  5. ログ: Worker → Logs(wrangler.toml の observability で有効化済み)。event:"tool_call" で絞ると呼び出し数が見える
B. Vercel
  1. vercel.com → Add New Project → リポジトリ stock-trading- を Import
  2. Root Directory を mcp に変更、Framework Preset は Other
  3. Deploy → https:// .vercel.app/mcp がエンドポイント
  4. ログ: Project → Logs(Hobby は保持1時間なので、集計したい場合は下の LOG_WEBHOOK を使う)
動作確認(デプロイ後にブラウザで開くだけ)
  • https://ruletrade.jp/mcp/health → "ok": true なら完了
  • Worker 直の https://ruletrade-mcp. .workers.dev/health でも同じものが見える(切り分け用)
接続(正規URLを使う。*.workers.dev は案内しない)
  • Claude(claude.ai): 設定 → コネクタ → カスタムコネクタを追加 → URL に https://ruletrade.jp/mcp
  • Claude Code: claude mcp add --transport http ruletrade https://ruletrade.jp/mcp
  • 最初に list_tools_guide を呼ぶよう initialize の instructions で案内している

環境変数(すべて任意)

変数用途
DATA_BASEJSONの取得元(既定: GitHub raw の docs/)。リポジトリ非公開化時に差し替え
ANOMALY_URL検証JSONを別配信先に置く場合に指定。get_anomaly_summary の jinx_verification_external にそのまま入る(通常は不要。既定は docs/anomaly_results.json)
LOG_WEBHOOK呼び出しログ(1行JSON)をPOSTする先。GAS/Slack/Sheets 等で集計したい場合
CACHE_TTL_MSインスタンス内キャッシュ(既定 60000)

呼び出しログの形: {"ts","event":"tool_call","tool","args","ok","ms","scrubbed","client"} (initialize 時は clientInfo も記録。実際にどう使われているかを見るための数字)

ローカル

cd mcp

npm test # 実際の docs/*.json をフィクスチャに35テスト(推奨語ゼロ・銘柄コードゼロの検査を含む) node dev.js # http://localhost:8787/mcp curl -s localhost:8787/health curl -s -X POST localhost:8787/mcp -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_market_regime","arguments":{"history_days":5}}}'

今後

  • run_rule_backtest は、検証基盤(backtest_grid)ができた時点で検討。エンジンは二重に作らない
  • Week 1 は「読むだけ」。書き込み・発注・個別助言に相当する機能は入れない
Ask PopNx