Report 01M7B5TM7C5BQ63QMRFMX7ERCS · checks-v2
Kadal Store MCP server: automated checks
What HostedMCP checked on 13 Nov 2026, 19:23 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
- 13 Nov 2026, 19:23 UTC
- Commit
- —
- Package
- @kadal/store · 0.1.1
- Methodology
- checks-v2
What to fix for a higher score
One check can earn more points. The next scan runs within a week, or right after the repository changes.
- 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
30 / 30 points- PassSource repository linked and reachable10 pts
kadalcc/store-cli is public and reachable
github.com/kadalcc/store-cli ↗ - PassPackage names this repository as its source5 pts
@kadal/store name kadalcc/store-cli as source
npmjs.com/package/@kadal/store ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for @kadal/store
npmjs.com/package/@kadal/store/v/0.1.1#provenance ↗ - Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-11
github.com/kadalcc/store-cli ↗ - 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 @kadal/store
- PassNo critical advisory in the package or its dependencies15 pts
99 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
2 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)
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.