cli@1.0.6

VERIFIED· startup only

Publisher claims: "Push OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher octri · publishing for 78 daysInstalls 0Last detonated 1 h ago
$claude mcp add cli -- npx -y @octri/cli
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
MONITORING_INGEST_TOKENMONITORING_TOKENOCTRI_API_KEYOCTRI_TOKEN or --reveal-tokenConfiguration, not credentials: MONITORING_ENVIRONMENT, MONITORING_RELEASE, MONITORING_URL, OCTRI_ALLOW_INSECURE_HTTP, OCTRI_API_URL, OCTRI_CONFIG_DIR, OCTRI_DEBUG, OCTRI_PROFILE, OCTRI_PROJECT_ID, TERM_PROGRAM, WT_SESSION
Where it talks to
octri.dev (its own)
What we saw when it ran
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for MONITORING_INGEST_TOKEN, MONITORING_TOKEN, OCTRI_API_KEY, OCTRI_TOKEN and talks to octri.dev. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets MONITORING_INGEST_TOKEN=octri.dev,MONITORING_TOKEN=octri.dev,OCTRI_API_KEY=octri.dev,OCTRI_TOKEN=octri.dev -- npx -y @octri/cli

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; startup only; authenticated tool behavior not tested) on 2026-11-21 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 26 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.2sprocessdependency install exit 0
26sclaimedstartup only: exited (0) before answering · --quiet Suppress non-essential output --plain Disable animation (implied by CI) --no-color Disable colour (or set NO_COLOR) Start here: octri auth login && octri projects use && octri lab run --lang go
26sprocessscript backend runs setup only
26sprocessno install scripts to re-run

Static findings

MEDIUM
File permission modification commandpackage.json:47 · File permission modification command — agent changes file ownership/permissions"build": "tsc -p tsconfig.json && chmod +x dist/bin.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

No other findings across 9,606 lines in 71 files.

Cost to the agent

Instructions loaded
≈85 tok
1 file · 71 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 @octri/cli@1.0.6 as of 47 min ago. This is the package itself, not its dependencies.