Octri API Docs
NPM · @OCTRI/MCP · SCANNED SEP 25
Search an Octri project's API docs and call its endpoints as tools, shaped by its SDK Studio config.
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 95 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 567 tokens (~81/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Octri API Docs MCP server?
Octri API Docs runs locally as an npm package, launched with npx -y @octri/mcp. 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/mcp
claude mcp add dev-octri-mcp -- npx -y @octri/mcp
{
"mcpServers": {
"dev-octri-mcp": {
"command": "npx",
"args": [
"-y",
"@octri/mcp"
]
}
}
} {
"servers": {
"dev-octri-mcp": {
"command": "npx",
"args": [
"-y",
"@octri/mcp"
]
}
}
} codex mcp add dev-octri-mcp -- npx -y @octri/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-octri-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@octri/mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-octri-mcp --command npx --arg -y --arg @octri/mcp
mcp_servers:
dev-octri-mcp:
command: "npx"
args: ["-y", "@octri/mcp"] {
"McpServers": {
"dev-octri-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@octri/mcp"
]
}
}
} assistant mcp add dev-octri-mcp -t stdio -c npx -a -y @octri/mcp
{
"mcpServers": {
"dev-octri-mcp": {
"command": "npx",
"args": [
"-y",
"@octri/mcp"
]
}
}
} 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.
- 25 Sept 26 71
First indexed and scored.
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 25 Sept 2026 · Analysed npm/@octri/mcp@1.1.1
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
get_changelog ~66
Get recent API changes and breaking changes
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_endpoint ~59
Get full documentation for a specific API endpoint
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The endpoint slug |
No output schema declared.
No examples provided.
get_guide ~93
Get the full content of a written guide (tutorial / conceptual doc) by its slug
| Name | Type | Req | Description |
|---|---|---|---|
| groupSlug | string | – | The guide's section slug, if it belongs to one |
| 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 | yes | The guide slug (from list_endpoints) |
No output schema declared.
No examples provided.
get_sdk_methods ~153
Show how to call this API through its generated SDKs. Ready-to-use code snippets per endpoint in every supported language. Use `slug` (from list_endpoints) to focus on one endpoint, and `language` (e.g. typescript, python, go) to focus on one language.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | Focus on a single endpoint by its slug. Omit to return all endpoints. |
No output schema declared.
No examples provided.
list_endpoints ~59
List all available API endpoints
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | Filter by section/tag name |
No output schema declared.
No examples provided.
list_sdks ~59
List the available SDK client libraries for this API (languages, versions, and download links)
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | – | Project to read. Optional — defaults to the project this server was started with. Only pass it to target a different project. |
No output schema declared.
No examples provided.
search_docs ~78
Search the API documentation for an endpoint or concept
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Natural language search query |
No output schema declared.
No examples provided.
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 npm package (@octri/mcp).
Is the Octri API Docs MCP server safe to use?
Octri API Docs scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 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 567 tokens of context every time the server is loaded.
Is the Octri API Docs MCP server still maintained?
Octri API Docs is still listed as active in the MCP registry. We last reached this channel on 25 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 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.