Report 01M7HXJJTNMHJEGTYBEYHAHA69 · checks-v2
Applitools MCP server: automated checks
What HostedMCP checked on 16 Nov 2026, 10:13 UTC. Every result links to the public source it came from, so you can check it yourself.
7 of 11 checks ran · 1 high finding · not a security audit
- Checked
- 16 Nov 2026, 10:13 UTC
- Commit
- —
- Package
- @applitools/mcp · 0.10.5
- Methodology
- checks-v2
What to fix for a higher score
4 checks can earn more points. The next scan runs within a week, or right after the repository changes.
- Build provenance (Sigstore attestation) up to +10 pts
Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - 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. - No hidden instructions to the model up to +15 pts
Remove text the model would read as an order from tool descriptions and the README: phrases like "ignore previous instructions", IMPORTANT tags, requests to hide things from the user, paths to credential files, and hidden Unicode characters.
Origin
10 / 15 points- PassSource repository linked and reachable10 pts
applitools/mcp is public and reachable
github.com/applitools/mcp ↗ - Not checkedPackage names this repository as its source5 pts
- Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
How to fix: Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - 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- Pass
- 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 @applitools/mcp
- PassNo critical advisory in the package or its dependencies15 pts
the package checked; no critical advisory
osv.dev ↗
Tool safety
5 / 20 points- FindingNo hidden instructions to the model15 pts
A tool description points at credential files
How to fix: Remove text the model would read as an order from tool descriptions and the README: phrases like "ignore previous instructions", IMPORTANT tags, requests to hide things from the user, paths to credential files, and hidden Unicode characters.
- PassDestructive tools are labelled5 pts
No tool named like delete, drop or exec
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
Starting the package
Listed its toolsWe installed @applitools/mcp 0.10.5 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
- 22
- Tracked since
- 16 Nov 2026
- Changes since then
- 0
- Version
- 0.10.4
- 16 Nov 2026First read22 tools recorded as the baseline0.10.4
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.