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.

Arketum

NPM · @RLABS-CL/ARKETUM

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

Available components

+3 this week 71 Trust /100

Last scanned (17 hours ago)

Scores higher than 42% of npm servers

Category Developer Tools

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • 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.Unverified
  • Actively maintained (last published 23 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability49
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 99% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • License in Provenance & TransparencyLicence 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.
  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 +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.

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

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

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

  • 11 Nov 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.

  • 9 Nov 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.

  • 7 Nov 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.

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 21 Nov 2026 · Analysed npm/@rlabs-cl/arketum@1.1.0

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~4,759 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
build ~4,759

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.

NameTypeReqDescription
acceptsboolean–`telemetry`: whether the person accepts (`true`) or not (`false`) sending the anonymous usage summary, with `quote`, their literal words. Never yours.
actionstring–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…
agentstring–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…
amendmentstring–`block`: the unit whose new definition amends the one being implemented, if the person chose to amend it (lp-f05); Arketum sets the reason.
artifactstring–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…
asksstring–`ask`: what the person is asked to decide (`no_e2e`: that a functional requirement does not admit an automated end-to-end test).
becausestring–`decide` at a requirement’s gate: why (required with `retire`, `decide` and `no_e2e`).
boundariesarray–`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…
catalogstring–`decide` when approving a step with a candidate archetype: the catalog where the person chose to publish it (the summary lists them).
chunkinteger–`audit`: the number of the chunk you request or report.
classificationobject–`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…
continuesstring–`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.
decisionstring–`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…
deletedarray–`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.
duestring–`defer`: the deadline, an ISO 8601 date.
emailstring–`identity`: the email the person said to identify themselves with.
evidencearray–`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…
fromstring–`decide` with `rejected` and `keep`: the earlier step to resume from, if the reason questions it.
fullboolean–`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).
gapsboolean–`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…
groupstring–`topic` without `topic`: the id of a group of open topics (the list, the batch and the overview give it), to list it whole.
idsarray–`requirement`: the requirements you look up, `<artifact>:<id>`, or the untyped intents, `<artifact>/<id>`.
inheritboolean–`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…
inventoriesarray–`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.
inventoryobject––
laneobject–`open`: the lane, by name and, if wanted, exact version.
languagestring–`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.
milestoneobject–`open`: the milestone, if the milestone step is chosen: `deployment`, `delivery` or `execution`, with its detail.
modestring–`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.
namestring–`identity`: the name the person said to identify themselves with (no login). Never one you inferred.
noRequirementarray–`close`: the touched artifacts whose changes touch no requirement (for example, scaffolding), each one with its reason.
notestring–`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).
objectivestring–`open`: what is to be achieved.
optioninteger–`open` with `topic`: the path of the proposal the person chose (from 1).
optionalarray–`open` and `rescope`: the optional steps of the lane that the unit includes.
optionsarray–`ask` with `asks: decision`: the options the person decides among.
ownerstring–`defer`: who answers for the debt.
pageinteger–`prd`: the page of the living PRD you request (from 1).
partobject–`elicit`: the elicitation part, with its `kind` (`situation`, `direction`, `conversation`, `sketch`, `signals`, `proposal`, `answers`, `consolidation`, `out_of_scope`, `request` or `reopen`) and its…
pathsarray–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/`…
policystring–`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.
proposalobject–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…
quotestring–`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…
reasonstring–`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`…
removearray–With `inherit`: the baseline ids that leave the level.
reportobject–`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…
requirementstring–`ask`: the requirement (`<artifact>:<id>`) the person is asked to decide about. `decide`: the requirement whose gate is decided.
resolutionobject–`decide` at a contradiction’s gate: how the person resolved it (which one prevails, which one is withdrawn, when each one applies, or defer).
retroactiveobject–`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…
revokeboolean–`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.
rolestring–`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…
rootstringyesThe project root.
scopestring–`decide` with `rejected`: whether the feature is kept or removed; both, with `reason`.
selfReviewstring–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…
signalsobject–`shapes`: the system’s signals (those the shapes declare, with their type), to know which shapes apply.
slugstring–`open`: the short name of the unit; its id is `<lane>-<slug>`.
stacksboolean–`shapes`: with `true`, it also lists the stacks (with their example tree) and the single-layer archetypes, which the architecture chooses.
stepstring–`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.
subagentsboolean–`mode`: whether your client can delegate to subagents (you declare it); without declaring it, Arketum suggests sequence.
summaryEveryinteger–`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…
summaryReplystring–`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…
textstring–`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,…
touchesarray–`open` and `rescope`: the project artifacts the unit touches. `decide` with `rejected` and `remove` in a system step: the ones that leave.
unitstring–The id of the work unit (`<lane>-<slug>`), in every action but `open` (in `requirement`, optional).
urgentboolean–`open`: whether it is urgent; only an urgent unit defers steps.
verdictstring–`decide` at a requirement’s gate: what the person decided in the chat (`undecided` withdraws the request without deciding). Never yours.
verdictsobject–`decide` with `step: confirmation`: for each functional requirement (`<artifact>:<id>`), `yes`, `no` or `later`, what the person answered; with `because` if any is `no`.
waitnumber–`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.
winnerstring–`choose`: the unit whose version the person chose in a semantic conflict (with `requirement` and `because`, their words). Never yours.

No output schema declared.

No examples provided.

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.

npm · @rlabs-cl/arketum

# add to Claude Code
claude mcp add cl-rlabs-arketum -- npx -y @rlabs-cl/arketum
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.