# katra (oci · ghcr.io/craigjmidwinter/katra-mcp:0.1.0)

A committed markdown dev log and task graph that agents read and write over MCP.

- Trust score: 51/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/craigjmidwinter/katra-mcp:0.1.0`: 51/100 (this document), [markdown](https://verifymcp.io/servers/craigjmidwinter-katra/ghcr-io-craigjmidwinter-katra-mcp-0-1-0.md), [page](https://verifymcp.io/servers/craigjmidwinter-katra/ghcr-io-craigjmidwinter-katra-mcp-0-1-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/craigjmidwinter/katra-mcp:0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 24 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1088 tokens (~72/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the katra MCP server?

katra runs locally as a container image, launched with docker run --rm -i ghcr.io/craigjmidwinter/katra-mcp:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add craigjmidwinter-katra -- docker run --rm -i ghcr.io/craigjmidwinter/katra-mcp:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "craigjmidwinter-katra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "craigjmidwinter-katra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add craigjmidwinter-katra -- docker run --rm -i ghcr.io/craigjmidwinter/katra-mcp:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "craigjmidwinter-katra": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  craigjmidwinter-katra:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "craigjmidwinter-katra": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "craigjmidwinter-katra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
```

## 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-09-20 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (15)

### `katra_append` (~75 tokens)

Append markdown to a draft. Defaults to the active draft if slug is omitted. Rich components are fenced code blocks: ```embed, ```compare, ```gallery, ```video, ```note, ```warning.

Input parameters:

- `markdown` (string, required): Markdown to append.
- `slug` (string): Target entry slug (default: active draft).

### `katra_article_new` (~55 tokens)

Create a new article (evergreen reference) node. Returns its slug.

Input parameters:

- `body` (string): Initial markdown body.
- `tags` (string): Comma-separated tags.
- `title` (string, required): Article title.

### `katra_capture` (~99 tokens)

Import a media file (image/gif/video/html) into the dev log and append it to a draft. Use this for screenshots, animation gifs, and interactive html artifacts.

Input parameters:

- `as` (string): Force kind: image|video|embed.
- `caption` (string): Caption for the media.
- `path` (string, required): Path to the media file to import.
- `slug` (string): Target entry slug (default: active draft).

### `katra_compare` (~78 tokens)

Import two images and append a before/after comparison slider to a draft.

Input parameters:

- `after` (string, required): Path to the 'after' image.
- `before` (string, required): Path to the 'before' image.
- `caption` (string): Caption for the comparison.
- `slug` (string): Target entry slug (default: active draft).

### `katra_decide` (~78 tokens)

Create a new decision (ADR) node. Returns its slug.

Input parameters:

- `body` (string): Initial markdown body.
- `entry` (string): The entry slug that recorded/occasioned this decision.
- `supersedes` (string): Comma-separated decision slug(s) this one supersedes.
- `title` (string, required): Decision title.

### `katra_epic_new` (~55 tokens)

Create a new epic node. Returns its slug.

Input parameters:

- `body` (string): Initial markdown body.
- `horizon` (string): Planning horizon: now|next|later.
- `title` (string, required): Epic title.

### `katra_get` (~32 tokens)

Get one entry's frontmatter and raw markdown body by slug.

Input parameters:

- `slug` (string, required): The entry slug.

### `katra_list` (~45 tokens)

List dev log entries (newest first). Returns slug, title, date, draft status, hashes and tags.

Input parameters:

- `drafts_only` (boolean): Only return unstamped drafts.

### `katra_new` (~89 tokens)

Create a new draft entry. Returns its slug. Write the *why*, not a paraphrased diff.

Input parameters:

- `body` (string): Initial markdown body.
- `featured` (boolean): Mark as a Deep Dive (long read).
- `summary` (string): One-line summary for the index.
- `tags` (string): Comma-separated tags.
- `title` (string, required): Entry title.

### `katra_nodes` (~72 tokens)

List nodes of a given type (newest first). Returns slug, title, type, date, status and other node-model fields. Omit type to list every node type.

Input parameters:

- `type` (string): Node type to list: entry|task|epic|decision|article. Empty = all types.

### `katra_stamp` (~72 tokens)

Stamp a draft with its commit hash(es) + computed diffstat, moving it from In Progress into the log. Defaults to HEAD and the active draft.

Input parameters:

- `hashes` (string): Comma-separated commit hash(es). Default: HEAD.
- `slug` (string): Target entry slug (default: active draft).

### `katra_task_list` (~47 tokens)

List task nodes (newest first). Optionally filter by status.

Input parameters:

- `status` (string): Filter to this status: todo|specced|doing|done|cut.

### `katra_task_new` (~125 tokens)

Create a new task node (status defaults to todo, or specced when spec is given). Returns its slug.

Input parameters:

- `body` (string): Initial markdown body.
- `effort` (string): Effort estimate: S|M|L.
- `epic` (string): Parent epic slug.
- `spec` (string): Spec artifact ref (a node slug in the katra, or a path relative to the repo root); creates the task already specced.
- `tags` (string): Comma-separated tags.
- `title` (string, required): Task title.

### `katra_task_set_status` (~59 tokens)

Set a task's status (todo|specced|doing|done|cut).

Input parameters:

- `slug` (string, required): Task slug.
- `status` (string, required): New status: todo|specced|doing|done|cut.

### `katra_task_spec` (~107 tokens)

Attach a spec artifact to a task. Advances todo/empty status to specced; leaves doing/done/cut alone (setting spec never moves status backwards). A ref that resolves to neither a node nor a file warns but still writes — `katra doctor` is the blocking check, not this.

Input parameters:

- `ref` (string, required): Spec ref: a node slug in the katra, or a path relative to the repo root.
- `slug` (string, required): Task slug.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/craigjmidwinter-katra/ghcr-io-craigjmidwinter-katra-mcp-0-1-0#diagnostics

## Score history

- 2026-09-20: 51
- 2026-09-19: 50
- 2026-09-18: 50
- 2026-09-17: 49
- 2026-09-16: 49
- 2026-09-15: 49
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 47
- 2026-09-11: 47
- 2026-09-10: 46
- 2026-09-09: 46
- 2026-09-08: 45
- 2026-09-07: 45
- 2026-09-06: 44
- 2026-09-05: 44
- 2026-09-04: 43
- 2026-09-03: 43
- 2026-09-02: 39
- 2026-09-01: 39
- 2026-08-31: 39
- 2026-08-30: 39
- 2026-08-29: 39
- 2026-08-28: 39
- 2026-08-27: 39
- 2026-08-26: 39

## Common questions

### What is the katra MCP server?

katra is an MCP server listed in the public MCP registry as io.github.craigjmidwinter/katra. A committed markdown dev log and task graph that agents read and write over MCP. This page covers its container image (ghcr.io/craigjmidwinter/katra-mcp:0.1.0).

### Is the katra MCP server safe to use?

katra scores 51 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 katra MCP server expose?

katra exposes 15 tools: katra_append, katra_article_new, katra_capture, katra_compare, katra_decide, and 10 more. Their descriptions and schemas cost roughly 1,088 tokens of context every time the server is loaded.

### Is the katra MCP server still maintained?

katra is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the katra MCP server under?

katra declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/craigjmidwinter/katra
- Website: https://midwinter.io/katra/
- Changelog RSS feed: https://verifymcp.io/servers/craigjmidwinter-katra/ghcr-io-craigjmidwinter-katra-mcp-0-1-0.xml
- Changelog JSON feed: https://verifymcp.io/servers/craigjmidwinter-katra/ghcr-io-craigjmidwinter-katra-mcp-0-1-0.json
- HTML version of this page: https://verifymcp.io/servers/craigjmidwinter-katra/ghcr-io-craigjmidwinter-katra-mcp-0-1-0