MCP/Risk

Directory / server

ai.getoptimal/optibot

registry.modelcontextprotocol.io, scanned 2026-09-11, tool surface via none

This directory entry reports an automated security scan of ai.getoptimal/optibot, scanned 2026-09-11. Trust grade C rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as ai.getoptimal/optibot. 1 finding
  • Registry entry: ai.getoptimal/optibot ↗
WARN Source repository is public and maintained §1.2

No public source repository could be identified for this server.
WARN Published package is consistent and attested §1.3
Minor integrity gaps: no npm provenance attestation. 6 findings
  • Package: @optimalai/optibot-mcp@1.5.0 ↗
  • Ecosystem: npm
  • Age: 176 days
  • Weekly downloads: 37
  • Repo field matches source repo: n/a
  • Build-provenance attestation: absent
UNVERIFIABLE Tool surface is inspectable and proportionate §2.1–§2.4

Tool surface could not be inspected (no reachable tools/list, no public package source). Per policy, unverifiability caps the overall grade.
INFO Transport & authentication §3

Local (stdio) server: runs with host-process privileges by design. Transport checks apply to remote servers; scrutiny shifts to §1/§2.
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for @optimalai/optibot-mcp @1.5.0 (npm).
UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

No server-supplied instructions or tool descriptions were obtainable to scan.

Score history

DateGradeScore
2026-09-11C71/100
2026-07-28C79/100
2026-07-27C79/100
2026-07-27C79/100
2026-07-26C79/100
2026-07-26C79/100
2026-07-25F38/100
2026-07-25F33/100
2026-07-25F38/100
2026-07-25F38/100
2026-07-24F38/100
2026-07-24F33/100
2026-07-24F38/100
2026-07-13F38/100
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.