Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

katra

OCI · GHCR.IO/CRAIGJMIDWINTER/KATRA-MCP:0.1.0 · SCANNED SEP 20

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

Available components

oci · ghcr.io/craigjmidwinter/katra-mcp:0.1.0 51
+3 this week 51 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • 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.Unverified
  • Install-script risk not yet assessed.Unverified
  • 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.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 24 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1088 tokens (~72/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

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.

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

# add to Claude Code
claude mcp add craigjmidwinter-katra -- docker run --rm -i ghcr.io/craigjmidwinter/katra-mcp:0.1.0
// .cursor/mcp.json
{
  "mcpServers": {
    "craigjmidwinter-katra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "craigjmidwinter-katra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
# add to Codex CLI
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/config.yaml
mcp_servers:
  craigjmidwinter-katra:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "craigjmidwinter-katra": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "craigjmidwinter-katra": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/craigjmidwinter/katra-mcp:0.1.0"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +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.

  • 18 Sept 26 +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.

  • 15 Sept 26 +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.

  • 13 Sept 26 +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.

  • 11 Sept 26 +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.

  • 9 Sept 26 +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.

  • 7 Sept 26 +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.

  • 5 Sept 26 +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.

Diagnostics

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 20 Sept 2026 · Analysed oci/ghcr.io/craigjmidwinter/katra-mcp:0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 15 exposed · ~1,088 tokens

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 →

Tool Tokens
katra_append ~75

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.

NameTypeReqDescription
markdownstringyesMarkdown to append.
slugstring–Target entry slug (default: active draft).

No output schema declared.

No examples provided.

katra_article_new ~55

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

NameTypeReqDescription
bodystring–Initial markdown body.
tagsstring–Comma-separated tags.
titlestringyesArticle title.

No output schema declared.

No examples provided.

katra_capture ~99

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.

NameTypeReqDescription
asstring–Force kind: image|video|embed.
captionstring–Caption for the media.
pathstringyesPath to the media file to import.
slugstring–Target entry slug (default: active draft).

No output schema declared.

No examples provided.

katra_compare ~78

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

NameTypeReqDescription
afterstringyesPath to the 'after' image.
beforestringyesPath to the 'before' image.
captionstring–Caption for the comparison.
slugstring–Target entry slug (default: active draft).

No output schema declared.

No examples provided.

katra_decide ~78

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

NameTypeReqDescription
bodystring–Initial markdown body.
entrystring–The entry slug that recorded/occasioned this decision.
supersedesstring–Comma-separated decision slug(s) this one supersedes.
titlestringyesDecision title.

No output schema declared.

No examples provided.

katra_epic_new ~55

Create a new epic node. Returns its slug.

NameTypeReqDescription
bodystring–Initial markdown body.
horizonstring–Planning horizon: now|next|later.
titlestringyesEpic title.

No output schema declared.

No examples provided.

katra_get ~32

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

NameTypeReqDescription
slugstringyesThe entry slug.

No output schema declared.

No examples provided.

katra_list ~45

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

NameTypeReqDescription
drafts_onlyboolean–Only return unstamped drafts.

No output schema declared.

No examples provided.

katra_new ~89

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

NameTypeReqDescription
bodystring–Initial markdown body.
featuredboolean–Mark as a Deep Dive (long read).
summarystring–One-line summary for the index.
tagsstring–Comma-separated tags.
titlestringyesEntry title.

No output schema declared.

No examples provided.

katra_nodes ~72

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.

NameTypeReqDescription
typestring–Node type to list: entry|task|epic|decision|article. Empty = all types.

No output schema declared.

No examples provided.

katra_stamp ~72

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.

NameTypeReqDescription
hashesstring–Comma-separated commit hash(es). Default: HEAD.
slugstring–Target entry slug (default: active draft).

No output schema declared.

No examples provided.

katra_task_list ~47

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

NameTypeReqDescription
statusstring–Filter to this status: todo|specced|doing|done|cut.

No output schema declared.

No examples provided.

katra_task_new ~125

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

NameTypeReqDescription
bodystring–Initial markdown body.
effortstring–Effort estimate: S|M|L.
epicstring–Parent epic slug.
specstring–Spec artifact ref (a node slug in the katra, or a path relative to the repo root); creates the task already specced.
tagsstring–Comma-separated tags.
titlestringyesTask title.

No output schema declared.

No examples provided.

katra_task_set_status ~59

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

NameTypeReqDescription
slugstringyesTask slug.
statusstringyesNew status: todo|specced|doing|done|cut.

No output schema declared.

No examples provided.

katra_task_spec ~107

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.

NameTypeReqDescription
refstringyesSpec ref: a node slug in the katra, or a path relative to the repo root.
slugstringyesTask slug.

No output schema declared.

No examples provided.

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.