Report 01M7EP0NMYXCF1X8T5DNQR5VC2 · checks-v2
CLI MCP server: automated checks
What HostedMCP checked on 15 Nov 2026, 04:04 UTC. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks
100/100
8 of 11 checks ran · 0 high findings · not a security audit
Origin
30 / 30 points- PassSource repository linked and reachable10 pts
cosyte/cli is public and reachable
github.com/cosyte/cli ↗ - PassPackage names this repository as its source5 pts
@cosyte/cli name cosyte/cli as source
npmjs.com/package/@cosyte/cli ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for @cosyte/cli
npmjs.com/package/@cosyte/cli/v/0.1.12#provenance ↗ - Pass
Practices
20 / 20 points- Pass
- PassOpenSSF Scorecard15 pts
OpenSSF Scorecard 7.5 / 10; weakest: Code-Review 0, CII-Best-Practices 0, Signed-Releases 0
scorecard.dev/viewer/?uri=github.com/cosyte/cli ↗
Supply chain
10 / 10 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from @cosyte/cli
- Not checkedNo critical advisory in the package or its dependencies15 pts
Tool safety
15 / 15 points- PassNo hidden instructions to the model15 pts
0 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- Not checkedDestructive tools are labelled5 pts
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
What these checks do not cover
- The server's code is not run and its 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.