Causal Mechanism Registry
REMOTE · ADENKARABAL.COM
A versioned registry of named causal mechanisms, each with definition, scope, boundary and test.
Available components
Last scanned (20 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1361 tokens (~170/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 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.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 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.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- “cite” reworded the description of “version” cosmetic
- “get_mechanism” reworded the description of “version” cosmetic
- “list_mechanisms” reworded the description of “version” cosmetic
- “search_mechanisms” reworded the description of “version” cosmetic
- 13 Nov 26 72
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 21 Nov 2026 · Probed https://adenkarabal.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=adenkarabal.com | CN=WE1,O=Google Trust Services,C=US | 16 Nov 2026 | 14 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | e9d49cfd94acd3c60e3865f448bd6b36 |
| SANs: adenkarabal.com, www.adenkarabal.com, *.www.adenkarabal.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of adenkarabal.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| adenkarabal.com. | No DS | 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=15552000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://adenkarabal.com/mcp | Verified | 200 | |
| http (plaintext) | http://adenkarabal.com/mcp | HTTPS enforced | 301 | https://adenkarabal.com/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 →
cite Citation ~127
Return the recommended citation line for a version, its version DOI (if it has one), the DOI that covers all versions, and the licence.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | – | Registry version, for example "1.4.1" (a leading "v" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | CC BY 4.0 attribution: how an answer that uses the entries names the source. |
| citation | string | yes | – |
| doi_all_versions | string | yes | – |
| doi_version | string|null | – | – |
| license | string | yes | – |
| license_url | string | – | – |
| note | string | – | – |
| released | string | – | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
| url | string | – | – |
| version | string | yes | – |
No examples provided.
fetch Fetch (connector form) ~69
Fetch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Entry identifier returned by search. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | CC BY 4.0 attribution: how an answer that uses the entries names the source. |
| id | string | yes | – |
| metadata | object | – | – |
| review_note | string | – | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_mechanism Get a mechanism ~203
Read 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 retired identifier is an error that names the replacement or the closest identifiers. Entries describe processes in general, not the present state of any country, market or asset.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Entry identifier, for example "energy_supply_shock". |
| version | string | – | Registry version, for example "1.4.1" (a leading "v" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | CC BY 4.0 attribution: how an answer that uses the entries names the source. |
| citation | string | yes | – |
| entry | object | yes | – |
| note | string | – | – |
| review_note | string | – | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
| url | string | yes | – |
| version | string | yes | – |
No examples provided.
list_mechanisms List mechanisms ~228
List 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.
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | – | Layer: core, social, extension, corpus or crisis_type. |
| review | string | – | Review state filter (versions 1.3.0 and later): all (default), accepted or in_review. The default covers every published entry and each result states its review state; entries in review are published… |
| version | string | – | Registry version, for example "1.4.1" (a leading "v" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1. |
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | – |
| in_review_not_shown | integer | – | – |
| note | string | – | – |
| returned | integer | yes | – |
| review | string | – | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
| total | integer | yes | – |
| version | string | yes | – |
No examples provided.
list_versions List versions ~62
List 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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| default_version | string | yes | – |
| doi_all_versions | string | – | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
| versions | array | yes | – |
No examples provided.
resolve_name Resolve a name or retired identifier ~66
Turn 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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Display name, identifier or retired identifier. Not empty. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| found | boolean | yes | – |
| id | string | – | – |
| layer | string | – | – |
| match | string | – | – |
| name | string | – | – |
| note | string | – | – |
| query | string | yes | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
| url | string | – | – |
| version | string | yes | – |
No examples provided.
search Search (connector form) ~84
Search 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 state of any country, market or asset.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query. Not empty. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | CC BY 4.0 attribution: how an answer that uses the entries names the source. |
| note | string | – | – |
| results | array | yes | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
No examples provided.
search_mechanisms Search mechanisms ~338
Search 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 are ignored and listed in the note. An entry matching every term ranks first; if none does, the closest partial matches are returned and the note says how many terms they match. Each result states its review state. Entries describe processes in general, not the present state of any country, market or asset.
| Name | Type | Req | Description |
|---|---|---|---|
| layer | string | – | Layer: core, social, extension, corpus or crisis_type. |
| limit | integer | – | Maximum entries returned (default 20). |
| query | string | yes | Name, identifier or words from the definition. Not empty. |
| review | string | – | Review state filter (versions 1.3.0 and later): all (default), accepted or in_review. The default covers every published entry and each result states its review state; entries in review are published… |
| version | string | – | Registry version, for example "1.4.1" (a leading "v" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | CC BY 4.0 attribution: how an answer that uses the entries names the source. |
| in_review_not_shown | integer | – | – |
| note | string | – | – |
| query | string | – | – |
| results | array | yes | – |
| returned | integer | yes | – |
| review | string | – | – |
| scope | string | – | Scope of the registry: what the entries are and are not. |
| total | integer | yes | – |
| version | string | yes | – |
No examples provided.
How do I install the Causal Mechanism Registry MCP server?
Causal Mechanism Registry is a hosted endpoint at https://adenkarabal.com/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 · adenkarabal.com
claude mcp add --transport http adenkarabal-causal-mechanism-registry 'https://adenkarabal.com/mcp'
What is the Causal Mechanism Registry MCP server?
Causal Mechanism Registry is an MCP server listed in the public MCP registry as io.github.adenkarabal/causal-mechanism-registry. A versioned registry of named causal mechanisms, each with definition, scope, boundary and test. This page covers its hosted endpoint (https://adenkarabal.com/mcp).
Is the Causal Mechanism Registry MCP server safe to use?
Causal Mechanism Registry scores 76 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 Causal Mechanism Registry MCP server expose?
Causal Mechanism Registry exposes 8 tools: search_mechanisms, get_mechanism, resolve_name, list_mechanisms, cite, and 3 more. Their descriptions and schemas cost roughly 1,177 tokens of context every time the server is loaded.
Does the Causal Mechanism Registry MCP server require authentication?
No. We connected to Causal Mechanism Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Causal Mechanism Registry MCP server still maintained?
Causal Mechanism Registry is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Causal Mechanism Registry MCP server?
VerifyMCP ran 13 checks on Causal Mechanism Registry, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.