# Octri API Docs (mcpb · octri-mcp-1.4.2.mcpb)

Search an Octri project's API docs and call its endpoints as tools, shaped by its SDK Studio config.

- Trust score: 54/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `octri-mcp-1.4.2.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/dev-octri-mcp/octri-mcp-2.md), [page](https://verifymcp.io/servers/dev-octri-mcp/octri-mcp-2)
- npm · `@octri/mcp`: 79/100, [markdown](https://verifymcp.io/servers/dev-octri-mcp/octri-mcp.md), [page](https://verifymcp.io/servers/dev-octri-mcp/octri-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/octridev/octri-mcp/releases/download/v1.4.2/octri-mcp-1.4.2.mcpb`
- Version: `1.4.2`
- Transport: `stdio`
- SHA-256: `a27c95d17be725a65a52eebbb2c856cfc6eb30140af14dda335aa00e1861f839`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 13/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - No install/post-install scripts declared.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 613 tokens (~87/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Octri API Docs MCP server?

Octri API Docs ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, a27c95d17be725a65a52eebbb2c856cfc6eb30140af14dda335aa00e1861f839; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/octridev/octri-mcp/releases/download/v1.4.2/octri-mcp-1.4.2.mcpb`
- SHA-256: `a27c95d17be725a65a52eebbb2c856cfc6eb30140af14dda335aa00e1861f839`

### Verify on macOS / Linux

```bash
echo "a27c95d17be725a65a52eebbb2c856cfc6eb30140af14dda335aa00e1861f839  octri-mcp-1.4.2.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\octri-mcp-1.4.2.mcpb).Hash -eq "a27c95d17be725a65a52eebbb2c856cfc6eb30140af14dda335aa00e1861f839"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 53, 0)

- [security regression] Provenance: unverified → fail
- [functional regression] Security disclosure: unverified → fail

### 2026-11-18 (score 53, +1)

- [security regression] Provenance: fail → unverified
- [functional regression] Security disclosure: fail → unverified

### 2026-11-15 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `search_docs` (~78 tokens)

Search the API documentation for an endpoint or concept

Input parameters:

- `limit` (number): Maximum number of results to return (default 5)
- `projectId` (string): Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
- `query` (string, required): Natural language search query

### `get_endpoint` (~59 tokens)

Get full documentation for a specific API endpoint

Input parameters:

- `projectId` (string): Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
- `slug` (string, required): The endpoint slug

### `list_endpoints` (~89 tokens)

List the API's endpoints and guides, grouped by section. A large API lists its sections with endpoint counts instead: pass `section` to list one of them.

Input parameters:

- `projectId` (string): Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
- `section` (string): Only the sections whose name contains this text

### `get_changelog` (~66 tokens)

Get recent API changes and breaking changes

Input parameters:

- `breakingOnly` (boolean): Only return entries with breaking changes (default false)
- `projectId` (string): Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.

### `list_sdks` (~59 tokens)

List the available SDK client libraries for this API (languages, versions, and download links)

Input parameters:

- `projectId` (string): Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.

### `get_guide` (~102 tokens)

Get the full content of a written guide (tutorial / conceptual doc) by its slug

Input parameters:

- `groupSlug` (string): The guide's group (list_endpoints shows it). Optional: found from the site's navigation when omitted.
- `projectId` (string): Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
- `slug` (string, required): The guide slug (from list_endpoints)

### `get_sdk_methods` (~160 tokens)

Show how to call this API through its generated SDKs. With `slug` (from list_endpoints or search_docs): ready-to-use code for that endpoint in every SDK language, or in one with `language` (e.g. typescript, python, go). Without `slug`: the index of SDK methods, one line per endpoint.

Input parameters:

- `language` (string): Focus on one SDK language (e.g. typescript, python, go). Omit for all supported languages.
- `projectId` (string): Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
- `slug` (string): One endpoint by its slug. Omit for the index of methods.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/dev-octri-mcp/octri-mcp-2#diagnostics

## Score history

- 2026-11-21: 54
- 2026-11-20: 54
- 2026-11-19: 53
- 2026-11-18: 53
- 2026-11-17: 52
- 2026-11-16: 52
- 2026-11-15: 52
- 2026-11-14: 51
- 2026-11-13: 51
- 2026-11-12: 50
- 2026-11-11: 50
- 2026-11-10: 49
- 2026-11-09: 49
- 2026-11-08: 48
- 2026-11-07: 48
- 2026-11-06: 47
- 2026-11-05: 47
- 2026-11-04: 46
- 2026-11-03: 46
- 2026-11-02: 45
- 2026-11-01: 45

## Common questions

### What is the Octri API Docs MCP server?

Octri API Docs is an MCP server listed in the public MCP registry as dev.octri/mcp. Search an Octri project's API docs and call its endpoints as tools, shaped by its SDK Studio config. This page covers its MCPB bundle (https://github.com/octridev/octri-mcp/releases/download/v1.4.2/octri-mcp-1.4.2.mcpb).

### Is the Octri API Docs MCP server safe to use?

Octri API Docs scores 54 out of 100 on VerifyMCP. 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 API Docs MCP server expose?

Octri API Docs exposes 7 tools: search_docs, get_endpoint, list_endpoints, get_changelog, list_sdks, and 2 more. Their descriptions and schemas cost roughly 613 tokens of context every time the server is loaded.

### What licence is the Octri API Docs MCP server under?

Octri API Docs 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 API Docs MCP server?

VerifyMCP ran 13 checks on Octri API Docs, covering Install scripts, Source repository, Provenance, License and 9 more. 3 items could not be completed, a gap on our side rather than a finding about Octri API Docs: Malware scan, Known CVEs and Dependency health. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/octridev/octri-mcp
- Website: https://octri.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-octri-mcp/octri-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-octri-mcp/octri-mcp-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-octri-mcp/octri-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/dev-octri-mcp/octri-mcp-2
