OctAPI MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Octapi business WhatsApp and customer-record tools: Do public business lookup and keyed customer operations retain distinct authority before outbound messaging?

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

Best fit

Access OctAPI data/services from an MCP client.

What we know

Radar identity confirms an npm MCP package named `octapi-mcp`, but sufficiently detailed first-party docs/repository material was not recovered in this research pass to safely describe its exact data domains, auth and write surface.

Maintenance / activity evidence

octapi-mcp 0.1.1 published 2026-09-14T14:18:40.300Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Unknown; preserve current profile authority rather than inventing read/write claims. Complete write authority is not verified.
Authentication not yet verified.
Unknown.

Insufficient first-party evidence.

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

All limitations / Review context

Do public business lookup and keyed customer operations retain distinct authority before outbound messaging?

The bounded review of the publisher's documented Octapi business WhatsApp and customer-record tools 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.

Insufficient first-party evidence.
Unknown; preserve current profile authority rather than inventing read/write claims.
Unknown.
Complete write authority is not verified.
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.
official docs/repository
tool inventory
auth
endpoint
data handling
write actions
Exact tool inventory, authentication, endpoint, data provenance, retention and mutation surface are unresolved.
Do not infer capabilities from the name alone.

Original activity observations

octapi-mcp 0.1.1 published 2026-09-14T14:18:40.300Z

Technical identity

npm/octapi-mcp

Exact implementation source: https://www.npmjs.com/package/octapi-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:octapi-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 ↗
octapi-mcp
Recorded package identity, distribution or download evidence.
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
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Claude Code only · Publisher instructions
claude mcp add octapi -- npx -y octapi-mcp mcp
Configure / authenticate
MCP100 setup guide
Consumer discovery works without key; for merchant tools `npx octapi-mcp login ok_live_...` or OCTAPI_API_KEY.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Check connection
Suggested check
npx octapi-mcp whoami; npx octapi-mcp tools. Do not book an appointment for a check.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `octapi-mcp` in Claude Code, remove its exact client entry with `claude mcp remove octapi-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Publisher install example registration name(s): octapi. The supplied removal example applies only to an existing Claude Code registration named octapi-mcp; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
```
claude mcp remove octapi-mcp
```

Official Documentation & Sources

What it does

Radar identity confirms an npm MCP package named `octapi-mcp`, but sufficiently detailed first-party docs/repository material was not recovered in this research pass to safely describe its exact data domains, auth and write surface.

Capability: Data & Databases
Resource type: MCP Server
Best fit: Access OctAPI data/services from an MCP client.

Representative uses

Use OctAPI through MCP once configured

Limitations

Exact tool inventory, authentication, endpoint, data provenance, retention and mutation surface are unresolved.
Do not infer capabilities from the name alone.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Unknown; preserve current profile authority rather than inventing read/write claims.
Data handling: Unknown.
Cost: unknown
Risk and cautions: Insufficient first-party evidence.

Access scope and cautions

Write actions: Not verified
Risk level: moderate

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

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: Use OctAPI through MCP once configured.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Unknown; preserve current profile authority rather than inventing read/write claims.

What limitations and risks should I check before use?

Insufficient first-party evidence. Exact tool inventory, authentication, endpoint, data provenance, retention and mutation surface are unresolved. Do not infer capabilities from the name alone. 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.