Skills/npm/obra-cto

obra-cto@0.3.0

VERIFIED

Publisher claims: "Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher get-obra · publishing for 136 daysInstalls 0Last detonated 5d ago
$claude mcp add obra-cto -- npx -y obra-cto
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso osv.dev, skool.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Connect it under the guard; read the third-party hosts first. The code names osv.dev, skool.com as well as its own vendor. The guard pins the network to the hosts the honeypot saw.

$vet-skills run --net declared -- npx -y obra-cto

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-09 and scored it 87/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 31 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
10sprocessdependency install exit 0
30sclaimed5 tools: scan_project, run_tests, check_dependencies, prepare_code_review, score_build_readiness
30sprocessscript backend runs setup only
30sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsdist/baf.js:47 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// a committed .env stays critical even if the code reads beautifully.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/baf.js:52 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filestitle: 'A .env file is committed to the project',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/index.js:315 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslines.push(`- Hygiene: committed .env ${s.committedEnvFile ? 'YES (risk)' : 'no'}; secret hits ${s.secrets.suspectCount}; TODO markers ${s.todos}`);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/review.js:158 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files'Sensitive data / leaks: any secrets, DB connection strings, or keys in code or a committed .env? Any endpoint returning passwords or PII? Secrets leaked in logs or errors?',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/review.js:203 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files'Are secrets (SSH keys, cloud credentials, .env) reachable from the agent execution context?',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/baf.js:59 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfindings.push('No committed .env file found.');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/scan.js:149 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif (/^\.env(\.|$)/.test(f) && !/\.example$/.test(f) && !/\.sample$/.test(f)) {Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/baf.js:55 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesfix: 'Remove it from the repo, rotate every value it held, and add .env to .gitignore. Commit a .env.example with empty keys instead.',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈82 tok
1 file · 18 in bundle
Tool list per prompt
≈1,209 tok
5 tools · 242 per tool
Handshake
479 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 307

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for obra-cto@0.3.0 as of 5d ago. This is the package itself, not its dependencies.

obra-cto@0.3.0 safety verdict: Verified — KillerSkills