Report 01M7HX08JEGCNMAWMTXG863A95 · checks-v2
Browserless MCP server: automated checks
What HostedMCP checked on 16 Nov 2026, 10:03 UTC. Every result links to the public source it came from, so you can check it yourself.
10 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 16 Nov 2026, 10:03 UTC
- Commit
- —
- Package
- @browserless.io/mcp · 1.48.0
- Methodology
- checks-v2
What to fix for a higher score
2 checks can earn more points. The next scan runs within a week, or right after the repository changes.
- Open source license (OSI) up to +5 pts
Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
- OpenSSF Scorecard up to +15 pts
Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions.
Origin
25 / 30 points- PassSource repository linked and reachable10 pts
browserless/browserless-mcp is public and reachable
github.com/browserless/browserless-mcp ↗ - PassPackage names this repository as its source5 pts
@browserless.io/mcp name browserless/browserless-mcp as source
npmjs.com/package/@browserless.io/mcp ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for @browserless.io/mcp
npmjs.com/package/@browserless.io/mcp/v/1.48.0#provenance ↗ - FindingOpen source license (OSI)5 pts
No license
How to fix: Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-13
github.com/browserless/browserless-mcp ↗ - Not checkedOpenSSF Scorecard15 pts
How to fix: Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions.
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from @browserless.io/mcp
- PassNo critical advisory in the package or its dependencies15 pts
the package checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
21 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- PassDestructive tools are labelled5 pts
No tool named like delete, drop or exec
Endpoint
5 / 5 points- PassRemote endpoint answers the MCP handshake5 pts
HTTPS endpoint answered 401 (sign-in required)
Starting the package
Listed its toolsWe installed @browserless.io/mcp 1.48.0 in an isolated container that could reach only the package registry, started it with no network and no credentials, and asked for its tools on 16 Nov 2026.
It answered and listed its tools without any credentials. The list is below.
Tool definitions
Read by starting the package in an isolated container with no network and no credentials. Each new release is read again, and a definition that changes shows up here with the versions.
- Tools now
- 21
- Tracked since
- 16 Nov 2026
- Changes since then
- 0
- Version
- 1.48.0
- 16 Nov 2026First read21 tools recorded as the baseline1.48.0
Remote servers are read when they answer without sign-in or with a token from the maintainer; packages are started in an isolated container. Definitions are third-party text, shown as written.
What these checks do not cover
- Tools are listed but never called, and the server's logic is not audited.
- Results describe the repository and package on the date above; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.