Optibot MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Optibot local-change and branch code reviews: Do uploaded diffs and returned findings retain repository scope and avoid exposing unrelated files?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Run AI code and security reviews while managing connected Optibot organization access.

What we know

AI code review for your AI assistant — review local changes, branch diffs, and patch files. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@optimalai/optibot-mcp 1.6.0 published 2026-09-17T05:17:08.916Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read local code changes and Optibot account/organization administration Writes: Trigger billed security scans; Create/delete API keys; Modify active organization selection.
Optibot API key
Sensitive access: Repository code/diffs, API keys, Organization information

Potential high-impact side effects: Trigger billed security scans, Create/delete API keys, Modify active organization selection.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do uploaded diffs and returned findings retain repository scope and avoid exposing unrelated files?

The bounded review of the publisher's documented Optibot local-change and branch code reviews and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potential high-impact side effects: Trigger billed security scans, Create/delete API keys, Modify active organization selection.
Read local code changes and Optibot account/organization administration
Optibot API key
Code/diffs and scan requests may transit Optibot cloud for AI review.
Reviewed write actions: Trigger billed security scans; Create/delete API keys; Modify active organization selection
Sensitive access: Repository code/diffs, API keys, Organization information
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
cost: plans, pay-per-call charges, and payment authorization details
Security scans may consume tokens or account balance
API-key administration is high privilege
Local repo patches may be shared with remote review services

Original activity observations

@optimalai/optibot-mcp 1.6.0 published 2026-09-17T05:17:08.916Z

Technical identity

npm/@optimalai/optibot-mcp

Exact implementation source: https://www.npmjs.com/package/@optimalai/optibot-mcp ↗
Reviewed resource type: MCP Server
Repository identity: Optimal-AI/optibot-mcp
Package identity: npm:@optimalai/optibot-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@optimalai/optibot-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
optimal-ai/optibot-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
OPTIBOT_API_KEY required; output remains unverified against live service.
publisher install or stdio launch · Publisher instructions
npx -y @optimalai/optibot-mcp

Configure / authenticate

MCP100 setup guide

Optibot security scan tools may consume billed tokens; do not run scans as a Setup test.

claude desktop or cursor mcpServers json · MCP100 composed guide

{
  "mcpServers": {
    "optibot": {
      "args": [
        "-y",
        "@optimalai/optibot-mcp"
      ],
      "command": "npx",
      "env": {
        "OPTIBOT_API_KEY": "YOUR_OPTIBOT_API_KEY"
      }
    }
  }
}

Check connection
Suggested check
After configuring OPTIBOT_API_KEY list authorized read-only status/tool metadata. Do not trigger metered AI security scans.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `optibot`, run `claude mcp remove optibot` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: Optibot official MCP tools `list_api_keys` and `delete_api_key` provide exact API-key revocation by key ID. `logout` removes saved local login (not equivalent to deleting all API keys).
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove optibot

Official Documentation & Sources

What it does

AI code review for your AI assistant — review local changes, branch diffs, and patch files. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Security & Testing
Resource type: MCP Server
Best fit: Run AI code and security reviews while managing connected Optibot organization access.

Representative uses

Review uncommitted and branch diffs
Review patch files
Trigger charged security scans
Create/list/delete API keys and switch organizations

Limitations

Security scans may consume tokens or account balance
API-key administration is high privilege
Local repo patches may be shared with remote review services

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optibot API key
Permissions: Read local code changes and Optibot account/organization administration
Data handling: Code/diffs and scan requests may transit Optibot cloud for AI review.
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Trigger billed security scans, Create/delete API keys, Modify active organization selection.

Access scope and cautions

Write actions: Trigger billed security scans Create/delete API keys Modify active organization selection
Sensitive access: Repository code/diffs API keys Organization information
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Review uncommitted and branch diffs; Review patch files; Trigger charged security scans; Create/list/delete API keys and switch organizations.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @optimalai/optibot-mcp. Recorded transport: stdio. Recorded environment-variable notes: OPTIBOT_API_KEY. No configuration values are supplied here. Prerequisites: MCP-capable client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Optibot API key

Can it modify data or perform write operations?

Documented write actions include: Trigger billed security scans; Create/delete API keys; Modify active organization selection. Recorded permission boundary: Read local code changes and Optibot account/organization administration

What data-handling boundary should I consider?

Code/diffs and scan requests may transit Optibot cloud for AI review. Recorded sensitive-access context: Repository code/diffs; API keys; Organization information.

What limitations and risks should I check before use?

Potential high-impact side effects: Trigger billed security scans, Create/delete API keys, Modify active organization selection. Security scans may consume tokens or account balance. API-key administration is high privilege. Local repo patches may be shared with remote review services. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.