SeleniumBase MCP
PYPI · SELENIUMBASE
Stealthy browser automation, testing, and web-scraping via CDP Mode.
Available components
Last scanned (56 minutes ago)
Scores higher than 16% of PyPI servers
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security75
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects filelock 4.1.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- Declares code that runs automatically (setup.py) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- Dependency health was assessed across the 76 of 79 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Provenance: fail → unverified ▼ security
- Package version: 4.57.0 → 4.57.1 functional
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 0
- Package version: 4.56.5 → 4.57.0 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- CVE-2026-112938 affects this package: high ▼ security
- CVE-2026-112915 affects this package: high ▼ security
- CVE-2026-112912 affects this package: high ▼ security
- CVE-2026-112911 affects this package: high ▼ security
- CVE-2026-112934 affects this package: high ▼ security
- CVE-2026-112910 affects this package: high ▼ security
- CVE-2026-112935 affects this package: high ▼ security
- CVE-2026-112909 affects this package: high ▼ security
- CVE-2026-112941 affects this package: high ▼ security
- CVE-2026-112939 affects this package: high ▼ security
- CVE-2026-112908 affects this package: high ▼ security
- Malware scan: unverified → pass ▲ security
- Package version: 4.56.4 → 4.56.5 functional
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
- Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 4.56.3 → 4.56.4 functional
- 25 Oct 26 −15
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/seleniumbase@4.57.1
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | pypi |
| Reason | Attestation not fetched |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
| setup_py | unreviewed | <setup.py, unreviewed> |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 19 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2g95-wg33-c5x2 | CVE-2026-112906 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-567q-5qvw-pf92 | CVE-2026-112907 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-6627-m3xw-93mp | CVE-2026-112908 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-69hj-f68j-2879 | CVE-2026-112909 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-8mx5-7m5m-r77g | CVE-2026-112910 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-9c4x-gm8v-wgc4 | CVE-2026-112911 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-9j6q-wvj5-jgjg | CVE-2026-112912 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-9vhv-jxww-xfm5 | CVE-2026-112913 | low | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-crv4-6mhj-j5jh | CVE-2026-112914 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N | yes |
| GHSA-cwqr-hh33-gh44 | CVE-2026-112915 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-fj95-fr6c-h845 | CVE-2026-112934 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H | yes |
| GHSA-fq56-3cx3-fjxp | CVE-2026-112935 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-jqc4-5cvw-7w85 | CVE-2026-112937 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L | yes |
| GHSA-m462-7rxw-wvpg | CVE-2026-112938 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H | yes |
| GHSA-rfpc-qcw5-3pc4 | CVE-2026-112939 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-v4x8-3wr5-3wq8 | CVE-2026-112940 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-wfhq-q4j2-c37m | CVE-2026-112941 | low | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-6w46-j5rx-g56g | CVE-2025-71176 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L | yes |
| PYSEC-2026-1845 | CVE-2025-71176 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 76 packages
| Packages resolved | 76 |
|---|---|
| Stale | 16 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the SeleniumBase MCP server?
SeleniumBase MCP runs locally as a PyPI package, launched with uvx seleniumbase. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · seleniumbase
claude mcp add seleniumbase-seleniumbase -- uvx seleniumbase
What is the SeleniumBase MCP server?
SeleniumBase MCP is listed in the public MCP registry as io.github.seleniumbase/seleniumbase. Stealthy browser automation, testing, and web-scraping via CDP Mode. This page covers its PyPI package (seleniumbase).
Is the SeleniumBase MCP server safe to use?
SeleniumBase MCP scores 32 out of 100 on VerifyMCP. We recorded 19 known advisories against it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the SeleniumBase MCP server still maintained?
SeleniumBase MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the SeleniumBase MCP server under?
SeleniumBase MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.