bisibility
bisibility is an MCP server published by bisibility.com, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does bisibility support the current MCP specification (2026-07-28)?
Not yet confirmed. bisibility is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is bisibility a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for bisibility (as of 2026-08-20).
How do I connect to bisibility?
bisibility is available via a hosted remote endpoint at https://bisibility.com/api/mcp, the package npm:@bisibility/mcp, the official MCP Registry under com.bisibility/mcp, the source repository at https://github.com/corgicorner/bisibility-mcp. Authentication: oauth. Transports: streamable-http.
Does bisibility support MCP revision 2025-11-25?
Yes. bisibility supports MCP revision 2025-11-25 (checked 2026-08-20).
Does bisibility support MCP revision 2026-07-28?
No. bisibility was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were bisibility's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Track keyword rankings, research SEO opportunities, and manage bisibility projects with AI agents.
Which MCP spec revisions does bisibility support?
bisibility has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is bisibility?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for bisibility
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 2
- Forks
- 0
- Last pushed
- (49 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- Apache-2.0
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: ai-agents, bisibility, mcp, mcp-server, model-context-protocol, rank-tracker, seo, seo-tools, serp — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.9.0- Last published
- First published
- Releases
- 15
- License (package)
- Apache-2.0
- Maintainers
- 1
- Direct dependencies
- 3
- Unpacked size
- 345 KB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for com.bisibility/mcp at version 0.6.2 - lists remote endpoint https://bisibility.com/api/mcp and repository https://github.com/corgicorner/bisibility-mcp - accessed
- Endpoint probe of https://bisibility.com/api/mcp - authorization required (HTTP 401, Bearer resource_metadata="https://bisibility.com/.well-known); capability set not observable without credentials - accessed
- npm registry metadata for @bisibility/mcp at published version 0.9.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed