@octri/mcp

MCPcommunity
v1.2.2dev.octriUnknownUpdated 5d agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3GitHub stars
5d agoLast update
Reads these credentials
  • OCTRI_API_TOKENAPI keyoptional

    Bearer or OAuth2 token for the documented API, not for Octri.

  • OCTRI_API_KEYAPI keyoptional

    API key for the documented API, not for Octri. Sent in the OCTRI_API_KEY_HEADER header.

  • OCTRI_API_PASSWORDAPI keyoptional

    Basic-auth password for the documented API.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authordev.octri
LicenseUnknown
Version1.2.2
Sourcenpm+mcp-registry
npm@octri/mcp
GitHuboctridev/octri-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface7 tools · none privileged
Security scan✓ Cleanv1.2.2 · todayHow well does this scan work?
EvalsNone
IndexedSep 27, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · none privileged
Statically extracted from the published packagev1.2.2 · 6h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_docsSearch the API documentation for an endpoint or concept

Search the API documentation for an endpoint or concept

No input schema was published for this tool.

get_endpointGet full documentation for a specific API endpoint

Get full documentation for a specific API endpoint

No input schema was published for this tool.

list_endpointsList all available API endpoints

List all available API endpoints

No input schema was published for this tool.

get_changelogGet recent API changes and breaking changes

Get recent API changes and breaking changes

No input schema was published for this tool.

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

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

get_sdk_methodsShow 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.

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.

No input schema was published for this tool.

7 of 7 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

7 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-17 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.