Case file No.356 · pypi · stdio

nodriver — Chrome browser automation

io.github.andresolbach/nodriver-mcp-server · v2.6.1

Chrome automation via nodriver: 70 tools, isolated browsers, profiles and configurable startup.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 4 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

328 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v2.6.1)Oct 17, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is nodriver — Chrome browser automation safe?

MCPWatch gives nodriver — Chrome browser automation a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does nodriver — Chrome browser automation have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package nodriver-mcp. That is not proof of safety.

When was nodriver — Chrome browser automation last updated?

The latest registry version is 2.6.1, published Oct 16, 2026. The last push to andresolbach/nodriver-mcp-server was on Oct 16, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does nodriver — Chrome browser automation use?

GitHub reports the license of andresolbach/nodriver-mcp-server as MIT.

Related servers

same publisher / similar score