Arketum

cl.rlabsPublished by rlabs.clv1.1.0Updated Oct 29, 2026

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

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Arketum is a local stdio MCP server that gives an assistant a verified lifecycle for building software with an agent: units, human gates and requirements.

What you can do
  • The listing names no individual tools, so capabilities come from the description only.
  • It is presented as a verified lifecycle for building software with an agent.
  • It works in units of work, with human gates and requirements as the organizing concepts.
  • It runs as a local process on the user's machine over stdio.
When to use it
Worth considering when you want an assistant to build software under a structured process with explicit requirements and checkpoints where a human approves before work continues, rather than free-form code generation.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package @rlabs-cl/arketum, so a Node.js runtime is needed. It is desktop-only and not web-executable. No authentication, environment variables or headers are declared.
Before you install
The listing gives no tool list, README or instructions, so what the server actually reads or writes on your machine cannot be verified before installing. It is described as gating software-building work, so expect it to influence or block steps in a development workflow; review its behavior in a test project first.

Installation

In SourceWeft

  1. Open Arketum in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.1.0LatestOct 29, 2026
  2. v1.0.2Oct 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.