REPORT 01M7CF2617SPPZ0H69H7YRBSFR · checks-v2
Laver MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 07:24 UTC for @laver/mcp 0.5.0. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks v2
100/100
7 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 07:24 UTC
- Commit
- —
- Package
- npm · 0.5.0
- Methodology
- checks-v2
Origin
20 / 20 points- PassSource repository linked and reachable10 pts
developyn/laver-mcp is public and reachable
github.com/developyn/laver-mcp ↗ - PassPackage names this repository as its source5 pts
@laver/mcp names developyn/laver-mcp as source
npmjs.com/package/@laver/mcp ↗ - Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
- Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-08-27
github.com/developyn/laver-mcp ↗ - Not checkedOpenSSF Scorecard15 pts
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from @laver/mcp
- PassNo critical advisory in the package or its dependencies15 pts
99 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
15 / 15 points- PassNo hidden instructions to the model15 pts
49 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 state on the date above and @laver/mcp 0.5.0; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.