# Causal Mechanism Registry (remote · adenkarabal.com)

A versioned registry of named causal mechanisms, each with definition, scope, boundary and test.

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `adenkarabal.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/adenkarabal-causal-mechanism-registry/adenkarabal.md), [page](https://verifymcp.io/servers/adenkarabal-causal-mechanism-registry/adenkarabal)

## Channel facts

- Endpoint: `https://adenkarabal.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http adenkarabal-causal-mechanism-registry 'https://adenkarabal.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "adenkarabal-causal-mechanism-registry": {
      "url": "https://adenkarabal.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "adenkarabal-causal-mechanism-registry": {
      "type": "http",
      "url": "https://adenkarabal.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.adenkarabal-causal-mechanism-registry]
url = "https://adenkarabal.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "adenkarabal-causal-mechanism-registry": {
      "type": "remote",
      "url": "https://adenkarabal.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add adenkarabal-causal-mechanism-registry --url 'https://adenkarabal.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  adenkarabal-causal-mechanism-registry:
    url: "https://adenkarabal.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "adenkarabal-causal-mechanism-registry": {
      "Transport": "http",
      "Url": "https://adenkarabal.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add adenkarabal-causal-mechanism-registry -t streamable-http -u 'https://adenkarabal.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "adenkarabal-causal-mechanism-registry": {
      "type": "http",
      "url": "https://adenkarabal.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 76, +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.

### 2026-11-19 (score 75, +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.

### 2026-11-17 (score 74, +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.

### 2026-11-15 (score 73, +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.

### 2026-11-14 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “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”

### 2026-11-13 (score 72)

First indexed and scored.

## MCP tools (8)

### `search_mechanisms` (~338 tokens)

Search mechanisms

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.

Input parameters:

- `layer` (string): Layer: core, social, extension, corpus or crisis_type.
- `limit` (integer): Maximum entries returned (default 20).
- `query` (string, required): 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.

Output parameters:

- `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)
- `returned` (integer)
- `review` (string)
- `scope` (string): Scope of the registry: what the entries are and are not.
- `total` (integer)
- `version` (string)

### `get_mechanism` (~203 tokens)

Get a mechanism

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.

Input parameters:

- `id` (string, required): 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.

Output parameters:

- `attribution` (string): CC BY 4.0 attribution: how an answer that uses the entries names the source.
- `citation` (string)
- `entry` (object)
- `note` (string)
- `review_note` (string)
- `scope` (string): Scope of the registry: what the entries are and are not.
- `url` (string)
- `version` (string)

### `resolve_name` (~66 tokens)

Resolve a name or retired identifier

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.

Input parameters:

- `name` (string, required): Display name, identifier or retired identifier. Not empty.

Output parameters:

- `candidates` (array)
- `found` (boolean)
- `id` (string)
- `layer` (string)
- `match` (string)
- `name` (string)
- `note` (string)
- `query` (string)
- `scope` (string): Scope of the registry: what the entries are and are not.
- `url` (string)
- `version` (string)

### `list_mechanisms` (~228 tokens)

List mechanisms

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.

Input parameters:

- `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.

Output parameters:

- `entries` (array)
- `in_review_not_shown` (integer)
- `note` (string)
- `returned` (integer)
- `review` (string)
- `scope` (string): Scope of the registry: what the entries are and are not.
- `total` (integer)
- `version` (string)

### `cite` (~127 tokens)

Citation

Return the recommended citation line for a version, its version DOI (if it has one), the DOI that covers all versions, and the licence.

Input parameters:

- `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.

Output parameters:

- `attribution` (string): CC BY 4.0 attribution: how an answer that uses the entries names the source.
- `citation` (string)
- `doi_all_versions` (string)
- `doi_version` (string|null)
- `license` (string)
- `license_url` (string)
- `note` (string)
- `released` (string)
- `scope` (string): Scope of the registry: what the entries are and are not.
- `url` (string)
- `version` (string)

### `list_versions` (~62 tokens)

List versions

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.

Output parameters:

- `default_version` (string)
- `doi_all_versions` (string)
- `scope` (string): Scope of the registry: what the entries are and are not.
- `versions` (array)

### `search` (~84 tokens)

Search (connector form)

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.

Input parameters:

- `query` (string, required): Search query. Not empty.

Output parameters:

- `attribution` (string): CC BY 4.0 attribution: how an answer that uses the entries names the source.
- `note` (string)
- `results` (array)
- `scope` (string): Scope of the registry: what the entries are and are not.

### `fetch` (~69 tokens)

Fetch (connector form)

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.

Input parameters:

- `id` (string, required): Entry identifier returned by search.

Output parameters:

- `attribution` (string): CC BY 4.0 attribution: how an answer that uses the entries names the source.
- `id` (string)
- `metadata` (object)
- `review_note` (string)
- `scope` (string): Scope of the registry: what the entries are and are not.
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/adenkarabal-causal-mechanism-registry/adenkarabal#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://adenkarabal.com/mcp
- Repository: https://github.com/adenkarabal/causal-mechanism-registry
- Website: https://adenkarabal.com/
- Changelog RSS feed: https://verifymcp.io/servers/adenkarabal-causal-mechanism-registry/adenkarabal.xml
- Changelog JSON feed: https://verifymcp.io/servers/adenkarabal-causal-mechanism-registry/adenkarabal/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/adenkarabal-causal-mechanism-registry/adenkarabal.json
- HTML version of this page: https://verifymcp.io/servers/adenkarabal-causal-mechanism-registry/adenkarabal
