World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
A versioned registry of named causal mechanisms, each with definition, scope, boundary and test.
作者による原文
これは「AI につながるアプリ」タブにあり、スターを使わず次の順で並びます
| 1. Claude のコネクタディレクトリにある | いいえ | |
|---|---|---|
| 2. チームが実際に試した | いいえ | |
| 3. タイのユーザー向け | いいえ | |
| 4. スターを除いた利用状況 | 20/100 | 人気 0 · 新しさ 12 · 応答中 8 · ユーザーのいいね +0 |
| 5. 登録日 | 2026-11-13 |
ユーザーのいいね: 0 · 順位に最大 5 点(1 人 1 点)加算。お金では買えません。
品質: 基本チェック 5/5 項目に合格(表示のみ、並び順には不使用)
使っているAIアプリを選んで、設定をコピーしてください。
ひとことで AI にインストールしてもらう
Causal Mechanism Registry をインストールして。https://mcp.popnx.com/i/adenkarabal-causal-mechanism-registry.md に従い、コマンドを見せて、私が OK するまで実行しないで。パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · AI が読む全文を見る
チェック 5/5 合格 · 質問内容は提供元のサーバー(adenkarabal.com)を通ります · ✓ コマンド確認済み 2026年11月13日
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 2 分
キー不要、インストール不要 · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
Causal Mechanism Registryhttps://adenkarabal.com/mcpClaude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します
+ConnectorsCausal Mechanism Registry
Causal Mechanism Registry を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Causal Mechanism Registry を使っていると言うか、回答に Causal Mechanism Registry のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT との接続はプランしだい
フル MCP:Web 版 ChatGPT の Business・Enterprise・Edu · Pro:読み取り/取得の権限で接続、データを変えるツールは使えないことがあります · Plus:公式ドキュメントで未確認。プラグイン画面にカスタム MCP を追加する項目があれば試せます · Web のみ
Plugins+Add custom MCP server
名前を入れ、Connection にアドレスを貼り付け、注意事項にチェックして Create as a plugin を押します
Causal Mechanism Registryhttps://adenkarabal.com/mcp新しいチャットを開き、入力前にプラグインの一覧から Causal Mechanism Registry を選びます
Causal Mechanism Registry を使って、私に何ができるか教えて、1 つやってみせて✓ ChatGPT が Causal Mechanism Registry を使っていると言うか、回答に Causal Mechanism Registry のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に OpenAI のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Claude Code につなげます · 約 2 分
キー不要、インストール不要
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user causal-mechanism-registry https://adenkarabal.com/mcpCausal Mechanism Registry が一覧にあり、接続済みと表示されれば OK です
Causal Mechanism Registry を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が Causal Mechanism Registry を使っていると言うか、回答に Causal Mechanism Registry のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 2 分
キー不要、インストール不要
Causal Mechanism Registry を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が Causal Mechanism Registry を使っていると言うか、回答に Causal Mechanism Registry のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 2 分
キー不要、インストール不要
Causal Mechanism Registry を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が Causal Mechanism Registry を使っていると言うか、回答に Causal Mechanism Registry のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください
Web 経由でつなぐアプリ用のアドレス
https://adenkarabal.com/mcpJSON 設定は下の「開発者向け」にあります
Claude Code
claude mcp add --transport http --scope user causal-mechanism-registry https://adenkarabal.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"causal-mechanism-registry": {
"url": "https://adenkarabal.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"causal-mechanism-registry": {
"type": "http",
"url": "https://adenkarabal.com/mcp"
}
}
}この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
ツールの名前と説明は、サーバーが2026年11月19日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
search_mechanismsSearch the registry by name, identifier or a word in the definition, scope, boundary or test. Returns matching entries with id, name, layer, kind, review state, name_test and the first sentence of the definition. A term matches the start of a word, terms shorter than 2 characters
get_mechanismRead one published entry in full: definition, scope, boundary, distinguishing test, related identifiers, phase roles and status fields, with its versioned GitHub address and a citation line. Does not filter by review state; the requested identifier always returns. An unknown or r
resolve_nameTurn a display name, an identifier or a retired identifier into the current identifier (for example export_pressure becomes export_earnings_shock). If nothing matches it says so and returns the closest three candidates.
list_mechanismsList entries with identifier, name, layer, kind and review state, optionally by layer and review state. The default lists every entry; with review=accepted the response states how many entries in review are not shown.
citeReturn the recommended citation line for a version, its version DOI (if it has one), the DOI that covers all versions, and the licence.
list_versionsList the published registry versions with release dates, version DOIs, entry counts and changes (kinds, the summary from CHANGELOG.md, the number of change items and a link to them). The first listed with default true is used when a version is not given.
searchSearch the registry; returns results with id, title and url. A thin wrapper over search_mechanisms for connectors that expect a search and a fetch tool. It looks in all review states and marks entries in review in the title. Entries describe processes in general, not the present
fetchFetch one entry by identifier as text with its url and metadata. A thin wrapper over get_mechanism for connectors that expect a search and a fetch tool. Entries describe processes in general, not the present state of any country, market or asset.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月20日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント adenkarabal で確認済みです
コードの最終更新:7 日前
CC-BY-4.0を使用
560ミリ秒で応答(HTTP 200)
サインイン不要
8件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/adenkarabal-causal-mechanism-registry)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック5項目のうち5項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は7 日前、最新バージョン(1.0.0)がレジストリに届いたのは7 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| これ Causal Mechanism Registry | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 動く場所 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 |
| キーが必要 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| Claude で + から追加 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| 基本チェック | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| ライセンス | CC-BY-4.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
In 1930 in Chicago, Samuel Insull borrowed money to buy back the shares a rival had gathered in his electricity empire, so as not to lose control of it. He meant to protect it. Two years later the empire collapsed, and that debt was one of the links that made the structure impossible to carry in a falling market.
In the 880s in China, the Tang court gave its regional commanders more troops and more authority to put down rebellions. The force that crushed the rebellions went on to break the centre itself apart.
In Zaire, Mobutu kept his own army weak on purpose for years, out of fear of a coup. When a rebellion backed by neighbouring countries began in 1996, the army barely resisted, and the regime fell within a year.
Three continents, more than a thousand years, three decisions, and one process: a move made to keep control destroys what it was meant to protect. History books rarely put these three events side by side. We do.
We study the crises of recorded history: bank failures and famines, epidemics and wars, collapsing states and natural disasters. Our list runs from a Mesopotamian debt cancellation around 2400 BC to the Valencia flood of 2024, and it grows every week. The goal has no fixed end.
We study people: what the decision-maker knew, what they could not do, and the trap they fell into.
We study the currents that shaped history: how an idea, a faith or a wave of migration prepared the ground for events.
We study inventions: which capability made what possible.
We study the events that faded before they became crises: where the chain stopped, and why.
We study the time between crises: how the condition one disaster leaves behind prepares the next.
And we take all of them apart into the processes that drove them. We call these processes mechanisms, and the connected archive of it all the corpus.
The same process is described in different words in every source, and a link without a name stays invisible.
Franklin National Bank failed in New York in 1974; Silicon Valley Bank failed in California in 2023. The losses came from different places: currency trading in one, long-term bonds that lost value as rates rose in the other. The process that brought each bank down was the same. Large depositors lost confidence and pulled their money at once. Give both events the same name, and what they share and where they part become visible across nearly fifty years.
So we give every mechanism a name, a definition, a boundary and a test. The vocabulary is open and free, and it belongs to no company, so that people and AI models can talk about crises with the same names.
Shared names make it possible to follow chains that are easy to miss.
In 1347 the Black Death swept across Europe. In 1377 the port of Ragusa (today's Dubrovnik) began to hold people arriving from plague areas before they could enter the city. That is how quarantine was born. In 2020, 643 years later, the world used the same tool again.
In 1994, armed groups settled in the camps in Zaire alongside the civilians fleeing the genocide in Rwanda. The armed organisation that continued in those camps prepared the ground for the Congo wars that began in 1996. The time between two crises is part of history too.
And some chains stop. In 2005 the large broker Refco went bankrupt. In its regulated futures arm, customers' assets were held apart from the firm's own accounts, so their positions were not frozen but moved quickly to another firm, and the failure did not spread through the system. Knowing where a chain stops is how we learn where it will not.
We hold all this experience up to today's world.
The signature: a dated picture, drawn from sourced evidence, of which processes are at work now and how strongly. Strength is an editorial intensity score, not a probability.
The simulation: it takes that picture as a starting point and tries, inside a model, the question "if this condition changes, what could be set in motion?" It is an experimental thinking tool, not a forecast.
| Corpus | The connected archive of crises, people, currents of thought, inventions and events that faded: from financial crises to natural disasters, from wars to epidemics. |
| Mechanism | A process that drives an event and recurs in other ages. |
| Vocabulary | The shared names of the mechanisms, each with its definition, boundary and test. Open and free. |
| Trap | The conditions a decision-maker is caught in: what they knew, what they could not do. |
| Current | An idea, a faith or a migration that prepares the ground for events. |
| Invention | A capability that makes something possible. |
| Negative space | Events that faded before they became crises, and where the chain stopped. |
| State | The condition a crisis leaves behind that prepares the next one. |
| Signature | A dated picture of which mechanisms are at work today, and how strongly. |
| Simulation | A thinking tool that starts from the signature and tries possible chains inside a model; not a forecast. |
This is a long project; it will take years. It has begun and it works, and we keep sharpening our lens with every step. Use it, correct it, support it.
[To the dashboard →](https://adenkarabal.com/pano/)
Shared names for the causal processes behind crises (economic, financial, political, social and humanitarian), each with a definition, a boundary and a test, so that people and models can name the same process in the same way.
Version 1.4.1 · 2026-11-13 · 233 entries in five layers · CC BY 4.0 · open to AI training
Mechanisms · mechanisms.json · Concepts · Principles · Agent guide · Agent skill · Seal · Changelog · Citation
Self-fulfilling run ·
self_fulfilling_run
Definition. Each individual's rational decision to exit encourages and accelerates others' exits until the run itself exhausts the resource.
Boundary. Exit is driven by expectations about others' exits and can strike an otherwise sound institution. Crowd action against a perceived injustice is subsistence_unrest_spiral; quiet convergence before the exit is herd_behavior.
Test. Withdrawals or hoarding accelerate because others are doing the same.
curl -s https://raw.githubusercontent.com/adenkarabal/causal-mechanism-registry/main/mechanisms.json \
| jq '.mechanisms[] | select(.id == "self_fulfilling_run")'
import json, urllib.request
reg = json.load(urllib.request.urlopen("https://raw.githubusercontent.com/adenkarabal/causal-mechanism-registry/main/mechanisms.json")) print({m["id"]: m for m in reg["mechanisms"]}"self_fulfilling_run")
When researchers, journalists and models describe the same crisis, they often give one process different names, or use one name for different processes. A fixed identifier with a definition, a boundary and a test lets two explanations be compared line by line, so that a disagreement is about evidence rather than about words.
The aim is a common vocabulary that belongs to no company, model or institution and that anyone can use, in the way that shared identifiers already work for software vulnerabilities (CVE) and diseases (ICD). Whether it becomes one depends on whether others use it. Institutions may propose what should be studied or added; they cannot determine definitions, boundaries, tests or findings, which are decided on evidence, not on who asks. The nature of institutional contributions is disclosed, and institutions are named only with their permission.
Events and figures show what happened. This registry names the recurring causal processes behind them, in the crises of recorded history and in today's world: for example fiscal dominance, contagion, liquidity stress or a self-fulfilling run. Each entry has a stable identifier, a definition, its scope, its boundary against neighbouring entries, and a test for when it applies.
The signature at adenkarabal.com includes 78 of these mechanisms (69 scored and 9 unknown in edition 2026-09-25); the others are named and defined but not scored in the current edition.
| Layer | Entries | In the signature | What it holds |
|---|---|---|---|
| Core causal mechanisms | 133 | 32 | Financial and macroeconomic channels |
| Social mechanisms | 32 | 20 | Political, social and state-capacity mechanisms |
| Signature extensions | 21 | 21 | Newer names in use in the signature; provisional |
| Corpus mechanisms | 42 | 0 | Tested in the research corpus, not yet in the signature; provisional |
| Crisis types | 5 | 5 | The event itself: war, famine, displacement, natural disaster, epidemic |
| Total | 233 | 78 |
MECHANISMS.md has every entry in full. mechanisms.json is the same content in machine-readable form. If the two differ, mechanisms.json takes precedence.
adenkarabal.com publishes Pano, a dashboard with a dated mechanism signature and its reading, evidence coverage by country and topic, evidence cards, a synthetic model with the experimental Run tool, and Tracking, which makes the research process visible. The public dashboard does not contain the entire research corpus. This repository is the open method layer behind it: the vocabulary, the concepts needed to read it, and the principles the work is kept under.
| In this repository (CC BY 4.0) | On adenkarabal.com |
|---|---|
| Names, definitions, scope, boundaries and tests | The signature: the names marked in_signature, each with a 0–100 score or marked unknown, and the edition's reading of the signature |
| Concepts: signature, score, evidence states | Evidence coverage by country and topic (open) |
| Principles, the agent guide and the agent skill | Source-reading titles and sourced evidence rows, except third-party text without permission to publish |
| A SHA-256 seal of the internal method | Tracking (the state of the work), and a synthetic model with the experimental Run tool, neither of which is evidence or a forecast |
The complete internal documentation of the method, as it stood on 2026-10-07, is sealed by SHA-256 digest in SEAL.md, so that it can be disclosed and checked later. What Tracking shows on adenkarabal.com does not replac