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.

CortexPilot Read-only MCP

PYPI · CORTEXPILOT-ORCHESTRATOR · SCANNED SEP 20

Read-only MCP server for CortexPilot workflows, queue state, proof, replay, and incident summaries.

Available components

pypi · cortexpilot-orchestrator 32
0 this week 32 Trust /100

Deprecated

This server is marked deprecated in the MCP registry.

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 Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects python-dotenv 1.2.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 7 of 89 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, 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 CortexPilot Read-only MCP server?

CortexPilot Read-only MCP runs locally as a PyPI package, launched with uvx cortexpilot-orchestrator. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · cortexpilot-orchestrator

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

  • 26 Aug 26 +15
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Aug 26 0
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → pass ▲ functional
  • 16 Aug 26 0
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: pass → unverified ▼ 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
  • 9 Aug 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 8 Aug 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 3 Aug 26 0
    • CVE-2026-48710 affects this package: medium ▼ security
    • CVE-2026-54282 affects this package: medium ▼ security
    • CVE-2026-48817 affects this package: medium ▼ security
    • CVE-2026-48818 affects this package: medium ▼ security
    • CVE-2026-54283 affects this package: medium ▼ security
    • CVE-2026-28684 affects this package: medium ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Dependency health: unverified → 0.97 ▲ 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 20 Sept 2026 · Analysed pypi/cortexpilot-orchestrator@0.1.0a4

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

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

Vulnerabilities 12 findings
ID CVE Severity Vector Fix available
GHSA-mf9w-mj56-hr94 CVE-2026-28684 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H yes
PYSEC-2026-2270 CVE-2026-28684 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H yes
GHSA-82w8-qh3p-5jfq CVE-2026-54283 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-86qp-5c8j-p5mr CVE-2026-48710 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-jp82-jpqv-5vv3 CVE-2026-54282 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wqp7-x3pw-xc5r CVE-2026-48818 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-x746-7m8f-x49c CVE-2026-48817 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-161 CVE-2026-48710 none yes
PYSEC-2026-2280 CVE-2026-48817 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-2281 CVE-2026-48818 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-248 CVE-2026-54282 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-249 CVE-2026-54283 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 89 packages
Packages resolved 89
Stale 6
No linked repository 1
Tree resolution Complete

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 CortexPilot Read-only MCP server?

CortexPilot Read-only MCP is listed in the public MCP registry as io.github.xiaojiou176-open/cortexpilot-readonly. Read-only MCP server for CortexPilot workflows, queue state, proof, replay, and incident summaries. This page covers its PyPI package (cortexpilot-orchestrator).

Is the CortexPilot Read-only MCP server safe to use?

CortexPilot Read-only MCP scores 32 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 20 September 2026. 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.

Is the CortexPilot Read-only MCP server still maintained?

CortexPilot Read-only MCP is marked deprecated 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 CortexPilot Read-only MCP server under?

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