Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.get-obra/obra-cto

NPM · OBRA-CTO · SCANNED AUG 3

Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine.

Available components

+19 this week 64 Trust /100
Trust breakdown (6 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 →

Supply Chain Security83
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known medium-severity CVE affects @hono/node-server 1.19.17, reached via @modelcontextprotocol/sdk > @hono/node-server. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 684 tokens (~136/item across 5 items; 5 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · obra-cto

# add to Claude Code
claude mcp add com-get-obra-obra-cto -- npx -y obra-cto
# add to Codex CLI
codex mcp add com-get-obra-obra-cto -- npx -y obra-cto
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-get-obra-obra-cto": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "obra-cto"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-get-obra-obra-cto --command npx --arg -y --arg obra-cto
# ~/.hermes/config.yaml
mcp_servers:
  com-get-obra-obra-cto:
    command: "npx"
    args: ["-y", "obra-cto"]
// mcp.json
{
  "mcpServers": {
    "com-get-obra-obra-cto": {
      "command": "npx",
      "args": [
        "-y",
        "obra-cto"
      ]
    }
  }
}
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.

  • 2 Aug 26 +59
    • GHSA-frvp-7c67-39w9 affects this package: medium security
    • Provenance: unverified → fail security
    • Known CVEs: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • Licence: Apache-2.0 functional
  • 31 Jul 26 −22
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 45

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-frvp-7c67-39w9 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

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

MCP tools — 5 exposed · ~684 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.

Tool Tokens
check_dependencies ~72

Query OSV.dev for known vulnerabilities in the project's locked dependencies, using exact versions from package-lock.json. Only package names and versions are sent, never your code. Real, current CVE data. Feed any findings into your security assessment.

NameTypeReqDescription
pathstringProject root. Defaults to the current working directory.

No output schema declared.

No examples provided.

prepare_code_review ~125

Select the highest-signal files (security-relevant paths, entry points, large files) and return their contents on this machine, with a review checklist. YOU, the host model, then read them and produce a structured security and architecture assessment, which you pass to score_build_readiness as `qualitative`. This is what upgrades those dimensions from inferred (grade C) to verified (grade A). Files stay local.

NameTypeReqDescription
max_filesnumberMaximum files to return (default 12).
pathstringProject root. Defaults to the current working directory.

No output schema declared.

No examples provided.

run_tests ~188

Run the project's test suite on this machine and parse pass/fail counts. This EXECUTES the project's own test command (for example `npm test`, which runs whatever that script defines), so only approve it for a project you trust to run. Your host asks before it runs. A green suite is the strongest grade-A reliability evidence the Obra CTO Score can use. Pass the result numbers to score_build_readiness.

NameTypeReqDescription
acknowledge_riskbooleanOnly relevant if the malware tripwire flagged this repo as dangerous. Running the test command would execute the flagged code. Set true ONLY after you have inspected the findings and are running in a…
commandstringOverride the test command (e.g. "pytest -q"). Defaults to the detected command.
pathstringProject root. Defaults to the current working directory.

No output schema declared.

No examples provided.

scan_project ~80

Read a local project and return mechanical Build Readiness signals: file and line counts, languages, test files, CI config, lockfile, docs, and a redacted scan for hardcoded secrets. Returns signals only, never your source. Run this first.

NameTypeReqDescription
pathstringAbsolute path to the project root. Defaults to the current working directory.

No output schema declared.

No examples provided.

score_build_readiness ~219

Produce the Obra CTO Score (0 to 100) with a per-dimension breakdown, evidence grades, and a Top Risks register. Scan runs automatically. If you ran run_tests first, pass its numbers so reliability becomes grade-A evidence.

NameTypeReqDescription
pathstringProject root. Defaults to the current working directory.
qualitativeobjectYour structured security and architecture assessment from prepare_code_review. Supplying it upgrades those dimensions to grade A.
stagestringCalibrate expectations to your stage: prototype, mvp, or growth. Defaults to a detected guess.
tests_failednumberFailing tests, from a prior run_tests call.
tests_passednumberPassing tests, from a prior run_tests call.
tests_totalnumberTotal tests, from a prior run_tests call.
write_reportbooleanWrite the report to .obra/ in the project (default true), so the Obra CFO can read it later. Set false to skip writing.

No output schema declared.

No examples provided.