REPORT 01M7C9B2DSA4T8F688RR4FZCZA · checks-v2
PairOnce MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 05:44 UTC for paironce 0.11.4. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks v2
100/100
8 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 05:44 UTC
- Commit
- —
- Package
- npm · 0.11.4
- Methodology
- checks-v2
Origin
30 / 30 points- PassSource repository linked and reachable10 pts
paironce/cli is public and reachable
github.com/paironce/cli ↗ - PassPackage names this repository as its source5 pts
paironce names paironce/cli as source
npmjs.com/package/paironce ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for paironce
npmjs.com/package/paironce/v/0.11.4#provenance ↗ - Pass
Practices
5 / 5 points- Pass
- 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 paironce
- PassNo critical advisory in the package or its dependencies15 pts
21 resolved dependencies checked; no critical advisory
osv.dev ↗
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 state on the date above and paironce 0.11.4; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.