browser-gateway
browser-gateway is an MCP server published by browser-gateway, 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 browser-gateway support the current MCP specification (2026-07-28)?
Not yet confirmed. browser-gateway 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 browser-gateway a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for browser-gateway (as of 2026-08-20).
How do I connect to browser-gateway?
browser-gateway is available via the package npm:browser-gateway, the official MCP Registry under io.github.browser-gateway/browser-gateway, the source repository at https://github.com/browser-gateway/browser-gateway. Authentication: unknown. Transports: stdio.
Does browser-gateway support MCP revision 2025-11-25?
Yes. browser-gateway supports MCP revision 2025-11-25 (checked 2026-08-20).
Does browser-gateway support MCP revision 2026-07-28?
No. browser-gateway was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were browser-gateway's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.
Which MCP spec revisions does browser-gateway support?
browser-gateway 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 browser-gateway?
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 browser-gateway
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
- 6
- Forks
- 1
- Last pushed
- (38 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: agent, browser, browser-automation, cdp, chrome-devtools-protocol, headless, load-balancer, mcp, mcp-server, playwright, puppeteer — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.4.16- Last published
- First published
- Releases
- 36
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 13
- Unpacked size
- 15.2 MB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.browser-gateway/browser-gateway at version 0.4.0 - lists package npm:browser-gateway and repository https://github.com/browser-gateway/browser-gateway - accessed
- npm registry metadata for browser-gateway at published version 0.4.13, 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