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.

CLEO MCP Server

NPM · @CLEOCODE/CLEO · SCANNED SEP 22

Task management for AI coding agents — CQRS 2-gateway pattern, 200 ops across 10 domains

Available components

npm · @cleocode/cleo 0
0 this week 0 Trust /100

Recent critical change

Known CVEs (2 Aug 2026). See the changelog before you install this server.

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 Security67
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
  • Dependency health was assessed across the 154 of 156 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency71
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to kryptobaseddev/cleo). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the CLEO MCP Server server?

CLEO MCP Server runs locally as an npm package, launched with npx -y @cleocode/cleo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @cleocode/cleo

# add to Claude Code
claude mcp add kryptobaseddev-cleo-mcp-server -- npx -y @cleocode/cleo
// .cursor/mcp.json
{
  "mcpServers": {
    "kryptobaseddev-cleo-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cleocode/cleo"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "kryptobaseddev-cleo-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cleocode/cleo"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add kryptobaseddev-cleo-mcp-server -- npx -y @cleocode/cleo
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kryptobaseddev-cleo-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cleocode/cleo"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add kryptobaseddev-cleo-mcp-server --command npx --arg -y --arg @cleocode/cleo
# ~/.hermes/config.yaml
mcp_servers:
  kryptobaseddev-cleo-mcp-server:
    command: "npx"
    args: ["-y", "@cleocode/cleo"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "kryptobaseddev-cleo-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@cleocode/cleo"
      ]
    }
  }
}
# add to Vellum
assistant mcp add kryptobaseddev-cleo-mcp-server -t stdio -c npx -a -y @cleocode/cleo
// mcp.json
{
  "mcpServers": {
    "kryptobaseddev-cleo-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cleocode/cleo"
      ]
    }
  }
}
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.

  • 19 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 18 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 12 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Aug 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Aug 26 0
    • Known CVEs: unverified → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Provenance: unverified → pass ▲ security
    • Install scripts: unverified → partial ▲ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • The scripts that run when this package is installed changed: postinstall security
    • The attested source repository moved: kryptobaseddev/cleo security
    • License: unverified → pass ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: MIT functional
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 22 Sept 2026 · Analysed npm/@cleocode/cleo@2026.3.35

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo kryptobaseddev/cleo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/kryptobaseddev/cleo/.github/workflows/release.yml@refs/tags/v2026.3.35
Rekor log index 1122299743
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:e13947f0baa12cf0936c8d417b9a4cf27aa58d51a86fc457b2de08192d17c592e427bbe9da9dbe8921fbac453c4794a2a2a733edfff1d6aa82cb2b7bf

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed node bin/postinstall.js

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-hffm-xvc3-vprc CVE-2026-6951 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 154 packages
Packages resolved 154
Deprecated 1
Stale 54
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the CLEO MCP Server server?

CLEO MCP Server is listed in the public MCP registry as io.github.kryptobaseddev/cleo-mcp-server. Task management for AI coding agents, CQRS 2-gateway pattern, 200 ops across 10 domains. This page covers its npm package (@cleocode/cleo).

Is the CLEO MCP Server server still maintained?

CLEO MCP Server is still listed as active in the MCP registry. We last reached this channel on 22 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 CLEO MCP Server server under?

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