com.get-obra/obra-cto
NPM · OBRA-CTO · SCANNED SEP 22
Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine.
Available components
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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 79 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the com.get-obra/obra-cto MCP server?
com.get-obra/obra-cto runs locally as an npm package, launched with npx -y obra-cto. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · obra-cto
claude mcp add com-get-obra-obra-cto -- npx -y obra-cto
{
"mcpServers": {
"com-get-obra-obra-cto": {
"command": "npx",
"args": [
"-y",
"obra-cto"
]
}
}
} {
"servers": {
"com-get-obra-obra-cto": {
"command": "npx",
"args": [
"-y",
"obra-cto"
]
}
}
} codex mcp add com-get-obra-obra-cto -- npx -y obra-cto
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-get-obra-obra-cto": {
"type": "local",
"command": [
"npx",
"-y",
"obra-cto"
],
"enabled": true
}
}
} openclaw mcp add com-get-obra-obra-cto --command npx --arg -y --arg obra-cto
mcp_servers:
com-get-obra-obra-cto:
command: "npx"
args: ["-y", "obra-cto"] {
"McpServers": {
"com-get-obra-obra-cto": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"obra-cto"
]
}
}
} assistant mcp add com-get-obra-obra-cto -t stdio -c npx -a -y obra-cto
{
"mcpServers": {
"com-get-obra-obra-cto": {
"command": "npx",
"args": [
"-y",
"obra-cto"
]
}
}
} 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.
- 22 Sept 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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/obra-cto@0.3.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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_dependencies Check dependencies for known CVEs ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Project root. Defaults to the current working directory. |
No output schema declared.
No examples provided.
prepare_code_review 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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_files | number | – | Maximum files to return (default 12). |
| path | string | – | Project root. Defaults to the current working directory. |
No output schema declared.
No examples provided.
run_tests 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.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_risk | boolean | – | Only 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… |
| command | string | – | Override the test command (e.g. "pytest -q"). Defaults to the detected command. |
| path | string | – | Project root. Defaults to the current working directory. |
No output schema declared.
No examples provided.
scan_project 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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Absolute path to the project root. Defaults to the current working directory. |
No output schema declared.
No examples provided.
score_build_readiness 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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Project root. Defaults to the current working directory. |
| qualitative | object | – | Your structured security and architecture assessment from prepare_code_review. Supplying it upgrades those dimensions to grade A. |
| stage | string | – | Calibrate expectations to your stage: prototype, mvp, or growth. Defaults to a detected guess. |
| tests_failed | number | – | Failing tests, from a prior run_tests call. |
| tests_passed | number | – | Passing tests, from a prior run_tests call. |
| tests_total | number | – | Total tests, from a prior run_tests call. |
| write_report | boolean | – | Write 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.
What is the com.get-obra/obra-cto MCP server?
com.get-obra/obra-cto is an MCP server listed in the public MCP registry as com.get-obra/obra-cto. Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine. This page covers its npm package (obra-cto).
Is the com.get-obra/obra-cto MCP server safe to use?
com.get-obra/obra-cto scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 com.get-obra/obra-cto MCP server expose?
com.get-obra/obra-cto exposes 5 tools: scan_project, run_tests, check_dependencies, prepare_code_review, score_build_readiness. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.
Is the com.get-obra/obra-cto MCP server still maintained?
com.get-obra/obra-cto 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 com.get-obra/obra-cto MCP server under?
com.get-obra/obra-cto declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.