# Arketum (npm · @rlabs-cl/arketum)

Verified lifecycle for building software with an agent: units, human gates, requirements.

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

## Components

- npm · `@rlabs-cl/arketum`: 71/100 (this document), [markdown](https://verifymcp.io/servers/cl-rlabs-arketum/rlabs-cl-arketum.md), [page](https://verifymcp.io/servers/cl-rlabs-arketum/rlabs-cl-arketum)

## Channel facts

- Registry: `npm`
- Package: `@rlabs-cl/arketum`
- Version: `1.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-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  - Actively maintained (last published 23 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 49/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4759 tokens (~4759/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

Arketum runs locally as an npm package, launched with npx -y @rlabs-cl/arketum. 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 cl-rlabs-arketum -- npx -y @rlabs-cl/arketum
```

### Cursor

```json
{
  "mcpServers": {
    "cl-rlabs-arketum": {
      "command": "npx",
      "args": [
        "-y",
        "@rlabs-cl/arketum"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cl-rlabs-arketum": {
      "command": "npx",
      "args": [
        "-y",
        "@rlabs-cl/arketum"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cl-rlabs-arketum -- npx -y @rlabs-cl/arketum
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cl-rlabs-arketum": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@rlabs-cl/arketum"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cl-rlabs-arketum --command npx --arg -y --arg @rlabs-cl/arketum
```

### Hermes

```yaml
mcp_servers:
  cl-rlabs-arketum:
    command: "npx"
    args: ["-y", "@rlabs-cl/arketum"]
```

### Netclaw

```json
{
  "McpServers": {
    "cl-rlabs-arketum": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@rlabs-cl/arketum"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cl-rlabs-arketum -t stdio -c npx -a -y @rlabs-cl/arketum
```

### Other

```json
{
  "mcpServers": {
    "cl-rlabs-arketum": {
      "command": "npx",
      "args": [
        "-y",
        "@rlabs-cl/arketum"
      ]
    }
  }
}
```

## 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 71, 0)

- [security] Stability: 0.97 → pass

### 2026-11-20 (score 71, +1)

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

### 2026-11-17 (score 70, +1)

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

### 2026-11-15 (score 69, +1)

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

### 2026-11-13 (score 68, +1)

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

### 2026-11-11 (score 67, +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-11-09 (score 66, +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-11-07 (score 65, +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.

## MCP tools (1)

### `build` (~4759 tokens)

The only door. Call without `inventory` to learn what comes next; call with `inventory` to deliver it. If the level does not reconcile with the previous one, it is rejected and does NOT advance. In a project with `.arketum/project.yaml`, the work goes in work units: `action` opens, resumes, submits, defers, pauses and closes them. When you start working on a project, bring up the person’s panel with `action: panel` and give them its address.

Input parameters:

- `accepts` (boolean): `telemetry`: whether the person accepts (`true`) or not (`false`) sending the anonymous usage summary, with `quote`, their literal words. Never yours.
- `action` (string): Optional, only with `.arketum/project.yaml`: what to do with a work unit. `status` (with `unit`, that unit; without it, the project, the unit index and the requirement index), `open`, `resume`, `subm…
- `agent` (string): Who you are (for example, `<client> / <model>`), marked as declared. With `open` (or with `resume`, if the unit has no agent yet on this connection), it signs what follows in that unit; in any other…
- `amendment` (string): `block`: the unit whose new definition amends the one being implemented, if the person chose to amend it (lp-f05); Arketum sets the reason.
- `artifact` (string): Optional, only in a project with `.arketum/project.yaml`: the artifact you ask about when you do not deliver an inventory. Without it, the answer is the project status. With `action: drift`, the arti…
- `asks` (string): `ask`: what the person is asked to decide (`no_e2e`: that a functional requirement does not admit an automated end-to-end test).
- `because` (string): `decide` at a requirement’s gate: why (required with `retire`, `decide` and `no_e2e`).
- `boundaries` (array): `close`: the boundaries of the touched artifacts, derived from the code and informative: per artifact, what is new or changed (`add`: `id`, `direction` `inbound`/`outbound`, `mechanism`, `counterpart…
- `catalog` (string): `decide` when approving a step with a candidate archetype: the catalog where the person chose to publish it (the summary lists them).
- `chunk` (integer): `audit`: the number of the chunk you request or report.
- `classification` (object): `open`: the class of the request against the requirement index and the index ids it names (`<artifact>:<id>`). Required in a lane with elicitation; it decides whether the lane fits. Classify after lo…
- `continues` (string): `open`: the adjustment that was exceeded (`excede_ajuste`) and that this unit continues: it is discarded when this one opens, and this one inherits its snapshot and its policy.
- `decision` (string): `decide`: the decision the person gave in the chat, only if your client cannot ask them. Never yours. They are the same four options as in the batch and the panel: `approved` (approve), `adjust` (wit…
- `deleted` (array): `close`: the files the unit deleted that were outside every root in its snapshot (paths from the project root): condition 5 does not count them.
- `due` (string): `defer`: the deadline, an ISO 8601 date.
- `email` (string): `identity`: the email the person said to identify themselves with.
- `evidence` (array): `submit` in an evidence or milestone step: each piece of evidence with the requirement it answers (`requirement`) and its class. An execution you run yourself and bring the command, output, exit code…
- `from` (string): `decide` with `rejected` and `keep`: the earlier step to resume from, if the reason questions it.
- `full` (boolean): `audit`: with `true`, it audits everything; without it, from newest to oldest, skipping what did not change since the last closed pass (except its neighbors by closeness).
- `gaps` (boolean): `audit`: the gaps and drifts Arketum computes (signals of the shape changed by hand, outputs of the shape without a stack with fixtures, what an architecture added after the authoring was approved, b…
- `group` (string): `topic` without `topic`: the id of a group of open topics (the list, the batch and the overview give it), to list it whole.
- `ids` (array): `requirement`: the requirements you look up, `<artifact>:<id>`, or the untyped intents, `<artifact>/<id>`.
- `inherit` (boolean): `submit` in a unit’s system step: `inventory.items` carries only what is new and what changed; the rest is inherited from the baseline (the same level of the artifact in the last closed unit that des…
- `inventories` (array): `submit` inside a unit: several levels in order, each one as a standalone delivery (with its own `inherit`, `remove`, `proposal` and `selfReview`). It stops at the first one that does not advance.
- `inventory` (object)
- `lane` (object): `open`: the lane, by name and, if wanted, exact version.
- `language` (string): `language`: the project language the person chose (`es` or `en`), with `quote`, her literal words; from then on everything Arketum generates for the project comes out in it. `open`: on the first `ope…
- `limit`: `delegate`: the delegation’s limit, in units opened under it (5, 10 or 20; 10 by default), or `no_limit`: in force until the person revokes it, with a summary in the batch every `summaryEvery` units.
- `milestone` (object): `open`: the milestone, if the milestone step is chosen: `deployment`, `delivery` or `execution`, with its detail.
- `mode` (string): `mode`: what the person chose for this session: `parallel` (the capture goes on while implementing) or `sequence` (it is implemented before defining further). Never yours.
- `name` (string): `identity`: the name the person said to identify themselves with (no login). Never one you inferred.
- `noRequirement` (array): `close`: the touched artifacts whose changes touch no requirement (for example, scaffolding), each one with its reason.
- `note` (string): `pause`: what is left and where to continue. `unblock`: how it was resolved (optional). `decide`: with `adjust`, what to adjust (required); with `dont_understand`, the person’s doubt (optional).
- `objective` (string): `open`: what is to be achieved.
- `option` (integer): `open` with `topic`: the path of the proposal the person chose (from 1).
- `optional` (array): `open` and `rescope`: the optional steps of the lane that the unit includes.
- `options` (array): `ask` with `asks: decision`: the options the person decides among.
- `owner` (string): `defer`: who answers for the debt.
- `page` (integer): `prd`: the page of the living PRD you request (from 1).
- `part` (object): `elicit`: the elicitation part, with its `kind` (`situation`, `direction`, `conversation`, `sketch`, `signals`, `proposal`, `answers`, `consolidation`, `out_of_scope`, `request` or `reopen`) and its…
- `paths` (array): The corpus paths. They are only used with a `.arketum/` without `project.yaml` (and not in the old format): they yield the legacy candidate of an archetype and its questionnaire. Without `.arketum/`…
- `policy` (string): `audit`: the source of the security rules the person named (their policies or their organization’s: a path, a URL or its name); without it, each chunk is judged against current general good practice.
- `proposal` (object): Optional. The starting inventory and the proposed change, so that the verdict tells what this change introduced from what was already broken. Inside a unit, Arketum sets the baseline (the level of th…
- `quote` (string): `decide`: the person’s literal words with which they already decided this gate in the conversation; it is recorded through the chat without asking them again. `telemetry`: those with which they accep…
- `reason` (string): `defer` and `rescope`: why. `decide` with `rejected`: the reason for the rejection, also required with `remove`. `block`: what you cannot resolve without the person (required, except with `amendment`…
- `remove` (array): With `inherit`: the baseline ids that leave the level.
- `report` (object): `audit`: the report of the `chunk` (`reviewer`, `reviewed`, `findings` and `consolidations`: what pursues the same thing, proposed as a consolidated PRD), the same as the retroactive validation’s. `d…
- `requirement` (string): `ask`: the requirement (`<artifact>:<id>`) the person is asked to decide about. `decide`: the requirement whose gate is decided.
- `resolution` (object): `decide` at a contradiction’s gate: how the person resolved it (which one prevails, which one is withdrawn, when each one applies, or defer).
- `retroactive` (object): `close`: the retroactive validation, if the unit brings requirements and there are earlier ones in what it touches (`close` without it gives the scope): who judged (`reviewer`; best, a subagent witho…
- `revoke` (boolean): `delegate`: withdraw the delegation in force; Arketum asks the person at every gate again. It leaves the same fact as `revoke` in the batch’s summary.
- `role` (string): `elicit`: the elicitation role that delivers the part (`analyst` or `architect`, declared). `status` with `unit`: that role’s package for the current stage; in the system step or the evidence step, a…
- `root` (string, required): The project root.
- `scope` (string): `decide` with `rejected`: whether the feature is kept or removed; both, with `reason`.
- `selfReview` (string): Optional. The answer to the self-review the archetype declares, in the exact format that was requested. It is collected, saved in `.arketum/` and shown. It is NOT evaluated and does NOT block: no ans…
- `signals` (object): `shapes`: the system’s signals (those the shapes declare, with their type), to know which shapes apply.
- `slug` (string): `open`: the short name of the unit; its id is `<lane>-<slug>`.
- `stacks` (boolean): `shapes`: with `true`, it also lists the stacks (with their example tree) and the single-layer archetypes, which the architecture chooses.
- `step` (string): `defer`: the step that is deferred. `decide`: the gate you presented (`lane` or the step’s id). `submit` with `evidence`: the step, if several share the requirement.
- `subagents` (boolean): `mode`: whether your client can delegate to subagents (you declare it); without declaring it, Arketum suggests sequence.
- `summaryEvery` (integer): `delegate` with `limit: no_limit`: every how many units opened under the delegation (5, 10 or 20, counting the unit where it is granted; 10 by default) the summary of what was approved on its own rea…
- `summaryReply` (string): `delegate`: what the person answered, through the chat, to the delegation summary that is due: `continue` or `revoke` (with `note`, their comment, if any). It leaves the same fact as the batch and th…
- `text` (string): `decide` with `decide`: the decided text, which creates the new version of the `decision`.
- `topic`: `topic`: leave a topic to discuss (`title`, `from`: `person` with their `words` verbatim, or `agent` if you propose it; `context`, `questions` and `proposal` optional: the unit that would tackle it,…
- `touches` (array): `open` and `rescope`: the project artifacts the unit touches. `decide` with `rejected` and `remove` in a system step: the ones that leave.
- `unit` (string): The id of the work unit (`<lane>-<slug>`), in every action but `open` (in `requirement`, optional).
- `urgent` (boolean): `open`: whether it is urgent; only an urgent unit defers steps.
- `verdict` (string): `decide` at a requirement’s gate: what the person decided in the chat (`undecided` withdraws the request without deciding). Never yours.
- `verdicts` (object): `decide` with `step: confirmation`: for each functional requirement (`<artifact>:<id>`), `yes`, `no` or `later`, what the person answered; with `because` if any is `no`.
- `wait` (number): `batch`: minutes (up to 30) the call waits for the person to save `.arketum/pending-decisions.md`; if the client cuts the call earlier, call again or ask them to let you know.
- `winner` (string): `choose`: the unit whose version the person chose in a semantic conflict (with `requirement` and `because`, their words). Never yours.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cl-rlabs-arketum/rlabs-cl-arketum#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 67
- 2026-11-11: 67
- 2026-11-10: 66
- 2026-11-09: 66
- 2026-11-08: 65
- 2026-11-07: 65
- 2026-11-06: 64
- 2026-11-05: 64
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 60
- 2026-10-27: 58
- 2026-10-26: 58
- 2026-10-25: 58
- 2026-10-24: 58
- 2026-10-23: 58

## Common questions

### What is the Arketum MCP server?

Arketum is an MCP server listed in the public MCP registry as cl.rlabs/arketum. Verified lifecycle for building software with an agent: units, human gates, requirements. This page covers its npm package (@rlabs-cl/arketum).

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

Arketum scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Arketum MCP server expose?

Arketum exposes 1 tool: build. Their descriptions and schemas cost roughly 4,759 tokens of context every time the server is loaded.

### Is the Arketum MCP server still maintained?

Arketum 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 Arketum MCP server?

VerifyMCP ran 14 checks on Arketum, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Arketum: License and Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@rlabs-cl/arketum
- Socket report: https://socket.dev/npm/package/@rlabs-cl/arketum
- Changelog RSS feed: https://verifymcp.io/servers/cl-rlabs-arketum/rlabs-cl-arketum.xml
- Changelog JSON feed: https://verifymcp.io/servers/cl-rlabs-arketum/rlabs-cl-arketum/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cl-rlabs-arketum/rlabs-cl-arketum.json
- HTML version of this page: https://verifymcp.io/servers/cl-rlabs-arketum/rlabs-cl-arketum
