Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Octri API Docs

MCPB · OCTRI-MCP-1.4.2.MCPB · 2 COMPONENTS

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

+3 this week 54 Trust /100

Last scanned (21 hours ago)

Scores higher than 86% of MCPB servers

Category Code Search and Documentation

Trust breakdown (7 categories)

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 Security13
  • 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.Unverified
  • 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).Unverified
  • No install/post-install scripts declared.Pass
  • 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).Unverified
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 613 tokens (~87/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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
What we tested

Checks we ran (13)

  • Install scripts
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityNo 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 in Supply Chain SecurityKnown 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).
  • Dependency health in Supply Chain SecurityDependency 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).

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 →

Changelog

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

    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.

  • 19 Nov 26 0
    • Provenance: unverified → fail ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 18 Nov 26 +1
    • Provenance: fail → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +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.

  • 7 Nov 26 +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.

Diagnostics

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 mcpb/https://github.com/octridev/octri-mcp/releases/download/v1.4.2/octri-mcp-1.4.2.mcpb@1.4.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 7 exposed · ~613 tokens

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 →

Tool Tokens
get_changelog ~66

Get recent API changes and breaking changes

NameTypeReqDescription
breakingOnlyboolean–Only return entries with breaking changes (default false)
projectIdstring–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

NameTypeReqDescription
projectIdstring–Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
slugstringyesThe endpoint slug

No output schema declared.

No examples provided.

get_guide ~102

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

NameTypeReqDescription
groupSlugstring–The guide's group (list_endpoints shows it). Optional: found from the site's navigation when omitted.
projectIdstring–Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
slugstringyesThe guide slug (from list_endpoints)

No output schema declared.

No examples provided.

get_sdk_methods ~160

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.

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

No output schema declared.

No examples provided.

list_endpoints ~89

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.

NameTypeReqDescription
projectIdstring–Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
sectionstring–Only the sections whose name contains this text

No output schema declared.

No examples provided.

list_sdks ~59

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

NameTypeReqDescription
projectIdstring–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

NameTypeReqDescription
limitnumber–Maximum number of results to return (default 5)
projectIdstring–Project to read. Optional: defaults to the project this server was started with. Only pass it to target a different project.
querystringyesNatural language search query

No output schema declared.

No examples provided.

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.

mcpb · octri-mcp-1.4.2.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

a27c95d17be725a65a52eebbb2c856cfc6eb30140af14dda335aa00e1861f839

macOS / Linux

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

Windows (PowerShell)

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

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

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.