Octri CLI
NPM · @OCTRI/CLI
Push OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors.
Available components
Last scanned (19 hours ago)
Scores higher than 73% of npm servers
Category Developer Tools
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 93 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 (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2080 tokens (~67/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 31 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
- Stability: 0.97 → pass security
- 19 Nov 26 −1
- Stability: pass → 0.97 functional
- 16 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 12 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 −2
- Stability: pass → 0.90 functional
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 21 Nov 2026 · Analysed npm/@octri/cli@1.0.6
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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
octri_diff_builds ~86
Compare two fetched builds file-by-file per language: which emitted files were added, removed or changed. The primary way to judge a generator change.
| Name | Type | Req | Description |
|---|---|---|---|
| from_build_id | string | yes | – |
| language | string | – | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| to_build_id | string | yes | – |
No output schema declared.
No examples provided.
octri_fetch_artifacts ~77
Download and extract a build's artifacts into the local cache so their files can be listed and read. Returns per-language file counts and a content fingerprint.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| languages | array | – | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_get_build ~56
One build's current state, including each language's lifecycle phase and any failure message.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_get_doc_page ~45
One documentation page by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
octri_get_issue ~77
One issue with its stack frames and recent events. A frame with resolved=true was de-minified against an uploaded source map; if none are, the symbols for that release were never uploaded.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_get_sdk_settings ~60
The project's persisted SDK Studio settings, per-endpoint overrides, revision, and last published release. The revision is required to write settings back.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_import_spec_url ~49
Import an OpenAPI spec from a public URL.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| url | string | yes | – |
No output schema declared.
No examples provided.
octri_list_builds ~47
Recent SDK builds with per-language status.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_doc_pages ~39
Documentation pages generated for the project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_generated_files ~69
List the files of a previously fetched build+language, with sizes. Call octri_fetch_artifacts first.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| language | string | yes | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_issues ~80
Grouped production errors, newest first. Each issue has an id usable with octri_get_issue.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | – |
| limit | number | – | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| range | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
octri_list_languages ~45
The SDK generator's language catalogue and the preference keys each language accepts.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_mcp_tools ~51
The MCP tool catalogue this project publishes to its own customers, derived from its SDK config.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_operations ~59
Every operation the parser found in the current spec, with method, path, operationId and deprecation, the list the SDK Studio renders.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_projects ~40
All projects in the organisation, with ids.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_sdk_repos ~45
Per-language GitHub repositories linked to the project's SDKs.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_list_specs ~42
OpenAPI specs uploaded to a project, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_monitoring_performance ~60
Slowest transactions (p50/p95) and suspected N+1 query patterns for the project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| range | string | – | – |
No output schema declared.
No examples provided.
octri_monitoring_releases ~63
Error rate, new issues and regressions per release. This is how you tell whether a deploy made things worse.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| range | string | – | – |
No output schema declared.
No examples provided.
octri_monitoring_summary ~85
Production health for the project: event count, error count, error rate and distinct issues over a window. Call this before reading issues. It tells you whether there is anything to look at.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| range | string | – | Time window. Defaults to 24h. |
No output schema declared.
No examples provided.
octri_preview_sdk ~114
Generate one language WITHOUT spending a build, and return the emitted file paths (and optionally contents). This is the fast loop for generator changes.
| Name | Type | Req | Description |
|---|---|---|---|
| include_content | boolean | – | Include file contents. Defaults to false (paths only) to keep the response small. |
| language | string | yes | Language id, e.g. `go`. |
| path_filter | string | – | Only return files whose path contains this substring. |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_push_spec ~64
Upload OpenAPI spec text (JSON or YAML) as the project's new current spec. Returns the created spec id.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw spec text. |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_query_logs ~94
Raw production events, unaggregated. Use when an issue's grouped view is not enough, e.g. to see every occurrence across releases.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | – |
| limit | number | – | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| query | string | – | Free-text match on the message. |
| range | string | – | – |
No output schema declared.
No examples provided.
octri_read_generated_file ~94
Read one generated file from a fetched build. This is how to inspect what the generator actually emitted.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| language | string | yes | – |
| max_bytes | number | – | Defaults to 200000. |
| path | string | yes | Path within the language's output tree. |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_retry_build ~73
Re-run only the named languages of an existing build, in place. Omit `languages` to retry exactly the ones that failed.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| languages | array | – | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_set_issue_status ~68
Triage an issue: resolve it, ignore it, or reopen it (status `unresolved`).
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| status | string | yes | – |
No output schema declared.
No examples provided.
octri_set_sdk_settings ~116
Write SDK Studio settings. Pass a full settings object (read it first with octri_get_sdk_settings and modify), plus the revision you read. A stale revision is rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| changelog | string | – | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| revision | number | yes | Revision from octri_get_sdk_settings. |
| settings | object | yes | Complete sdkSettings object. Replaces the stored one. |
| version | string | – | Optional release version. |
No output schema declared.
No examples provided.
octri_trigger_build ~87
Queue an SDK build for one or more languages. Returns a build id immediately; poll with octri_get_build or block with octri_wait_for_build.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | Language ids, e.g. ["go","rust"]. |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| version | string | – | – |
No output schema declared.
No examples provided.
octri_validate_spec ~51
Run the generator's validator against the project's current spec. Cheap; do this before spending a build.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
octri_wait_for_build ~83
Block until every language of a build reaches a terminal state, then return the final per-language result. Use after octri_trigger_build.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
| timeout_seconds | number | – | Defaults to 1800 (30 minutes). |
No output schema declared.
No examples provided.
octri_whoami ~61
The signed-in user, org, plan, API URL and currently selected project. Call this first to confirm which environment the session is pointed at.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project id. Optional, falls back to the CLI's selected project. |
No output schema declared.
No examples provided.
How do I install the Octri CLI MCP server?
Octri CLI runs locally as an npm package, launched with npx -y @octri/cli mcp serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @octri/cli
claude mcp add dev-octri-cli -- npx -y @octri/cli mcp serve
What is the Octri CLI MCP server?
Octri CLI is an MCP server listed in the public MCP registry as dev.octri/cli. Push OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors. This page covers its npm package (@octri/cli).
Is the Octri CLI MCP server safe to use?
Octri CLI scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Octri CLI MCP server expose?
Octri CLI exposes 31 tools: octri_whoami, octri_list_projects, octri_list_specs, octri_push_spec, octri_import_spec_url, and 26 more. Their descriptions and schemas cost roughly 2,080 tokens of context every time the server is loaded.
Is the Octri CLI MCP server still maintained?
Octri CLI is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Octri CLI MCP server under?
Octri CLI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Octri CLI MCP server?
VerifyMCP ran 16 checks on Octri CLI, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.