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 를 따라 하고, 명령을 먼저 보여 주고 내가 승인하면 실행해.내 컴퓨터에서 작업하는 AI(Claude Code, Cursor 등)에 붙여 넣으세요. 단계를 읽고 명령을 보여 준 뒤 승인을 기다립니다. 키도 가입도 필요 없습니다. · 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을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 Causal Mechanism Registry을 쓰고 있다고 하거나 답에 Causal Mechanism Registry 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT 연결은 요금제에 따라 달라요
전체 MCP: 웹 ChatGPT Business, Enterprise, Edu · Pro: 읽기/가져오기 권한으로 연결, 데이터를 바꾸는 도구는 안 될 수 있어요 · Plus: 공식 문서 미확인, 플러그인 화면에 사용자 지정 MCP 추가 항목이 보이면 시도해 볼 수 있어요 · 웹만
Plugins+Add custom MCP server
이름을 넣고 Connection에 주소를 붙여 넣은 뒤 경고에 체크하고 Create as a plugin을 누르세요
Causal Mechanism Registryhttps://adenkarabal.com/mcp새 채팅을 열고 입력 전에 플러그인 목록에서 Causal Mechanism Registry을 고르세요
Causal Mechanism Registry을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ 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이 목록에 있고 연결됨으로 보이면 돼요
Causal Mechanism Registry을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude Code가 Causal Mechanism Registry을 쓰고 있다고 하거나 답에 Causal Mechanism Registry 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Cursor에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Causal Mechanism Registry을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Cursor가 Causal Mechanism Registry을 쓰고 있다고 하거나 답에 Causal Mechanism Registry 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Cursor 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
VS Code에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Causal Mechanism Registry을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ VS Code가 Causal Mechanism Registry을 쓰고 있다고 하거나 답에 Causal Mechanism Registry 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 VS Code 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Windsurf, Zed, Gemini CLI 같은 다른 MCP 앱은 추가 방법이 저마다 달라요. 앱 목록에서 확인하세요
웹으로 연결하는 앱용 주소
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 사용
560ms 만에 응답(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를 받는 앱에서도 쓸 수 있어요. 예: 웹 ChatGPT(Business 이상은 전체 MCP, Pro는 읽기 전용).
같은 카테고리에는: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도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