Bisibility MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Bisibility preview keyword ranking and SEO tools: Do SDK-backed contracts remain stable during developer preview without overstating ranking estimates?

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

Best fit

SEO research, rank tracking and project management with optional read-only and toolset controls.

What we know

Stdio MCP over the Bisibility API for projects, keywords, checks, rankings, analytics, backlinks, alerts, team, providers, tokens and webhooks.

Maintenance / activity evidence

@bisibility/mcp 0.10.0 published 2026-09-09T09:16:14.594Z

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.
Potential broad SEO project/team/provider/token/webhook read-write depending on toolsets. Writes: Create/delete projects/keywords; Bulk delete/update keywords; Create/delete webhooks/alerts/saved views; Remove team/competitor; Disconnect providers; Revoke credentials/invites.
API key/PAT.
Sensitive access: SEO strategy, Team/account data, API credentials

Large write surface; enable read-only and narrow toolsets for research workflows.

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

All limitations / Review context

Do SDK-backed contracts remain stable during developer preview without overstating ranking estimates?

The bounded review of the publisher's documented Bisibility preview keyword ranking and SEO 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.

Large write surface; enable read-only and narrow toolsets for research workflows.
Potential broad SEO project/team/provider/token/webhook read-write depending on toolsets.
API key/PAT.
SEO project/keyword/alert content flows through Bisibility; provider-backed analysis can incur third-party cost.
Reviewed write actions: Create/delete projects/keywords; Bulk delete/update keywords; Create/delete webhooks/alerts/saved views; Remove team/competitor; Disconnect providers; Revoke credentials/invites
Sensitive access: SEO strategy, Team/account data, API credentials
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.
Default surface includes destructive tools unless read-only is enabled.
Domain overview calls can spend provider budget and require explicit max_cost_cents.
API-returned tracked content is untrusted model input.
Developer-preview status.

Original activity observations

@bisibility/mcp 0.10.0 published 2026-09-09T09:16:14.594Z

Technical identity

npm/@bisibility/mcp

Exact implementation source: https://www.npmjs.com/package/@bisibility/mcp ↗
Reviewed resource type: MCP Server
Repository identity: CorgiCorner/bisibility-mcp
Package identity: npm:@bisibility/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 ↗
@bisibility/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
Developer preview. Set BISIBILITY_API_KEY (project key or personal access token); BISIBILITY_BASE_URL optional. Use publisher documented Codex/Claude configuration.
publisher install or stdio launch · Publisher instructions
npx -y @bisibility/mcp
Configure / authenticate
MCP100 setup guide
Codex: publisher documents `codex mcp add bisibility --env BISIBILITY_API_KEY=<key> -- npx -y @bisibility/mcp`. API key may be a project key or personal access token.
Previously reviewed client configuration / prerequisites: BISIBILITY_MCP_TOOLSETS is optional toolset filter (e.g. projects,keywords,checks,rank-history). Prefer client-protected secret storage.
Check connection
Suggested check
Verify server/tool visibility then use a read-only projects or keyword listing; do not create monitoring checks.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `bisibility-mcp`, run `claude mcp remove bisibility-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove bisibility-mcp

Official Documentation & Sources

What it does

Stdio MCP over the Bisibility API for projects, keywords, checks, rankings, analytics, backlinks, alerts, team, providers, tokens and webhooks.

Capability: Search & Web
Resource type: MCP Server
Industry: Media & Marketing
Best fit: SEO research, rank tracking and project management with optional read-only and toolset controls.

Representative uses

Manage SEO projects/keywords/checks
Inspect rank history/backlinks/analytics
Create alerts/webhooks
Analyze domain overview and provider-backed data

Limitations

Default surface includes destructive tools unless read-only is enabled.
Domain overview calls can spend provider budget and require explicit max_cost_cents.
API-returned tracked content is untrusted model input.
Developer-preview status.

Reviewed access

Access & risk

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

Authentication: API key/PAT.
Permissions: Potential broad SEO project/team/provider/token/webhook read-write depending on toolsets.
Data handling: SEO project/keyword/alert content flows through Bisibility; provider-backed analysis can incur third-party cost.
Cost: usage_and_provider_cost
Risk and cautions: Large write surface; enable read-only and narrow toolsets for research workflows.

Access scope and cautions

Write actions: Create/delete projects/keywords Bulk delete/update keywords Create/delete webhooks/alerts/saved views Remove team/competitor Disconnect providers Revoke credentials/invites
Sensitive access: SEO strategy Team/account data API credentials
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: Manage SEO projects/keywords/checks; Inspect rank history/backlinks/analytics; Create alerts/webhooks; Analyze domain overview and provider-backed data.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @bisibility/mcp. Recorded transport: stdio. Recorded environment-variable notes: BISIBILITY_API_KEY; BISIBILITY_BASE_URL (optional); BISIBILITY_PROJECT_ID (optional); BISIBILITY_MCP_READ_ONLY (recommended when applicable); BISIBILITY_MCP_TOOLSETS (optional allowlist). No configuration values are supplied here. Prerequisites: Node.js 18+; Bisibility key. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Project key or personal access token.

Can it modify data or perform write operations?

Documented write actions include: Create/delete projects/keywords; Bulk delete/update keywords; Create/delete webhooks/alerts/saved views; Remove team/competitor; Disconnect providers; Revoke credentials/invites. Recorded permission boundary: Potential broad SEO project/team/provider/token/webhook read-write depending on toolsets.

What data-handling boundary should I consider?

SEO project/keyword/alert content flows through Bisibility; provider-backed analysis can incur third-party cost. Recorded sensitive-access context: SEO strategy; Team/account data; API credentials.

What limitations and risks should I check before use?

Large write surface; enable read-only and narrow toolsets for research workflows. Default surface includes destructive tools unless read-only is enabled. Domain overview calls can spend provider budget and require explicit max_cost_cents. API-returned tracked content is untrusted model input. Developer-preview status. 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.