REPORT 01M7CCRY1171VQ6KCV88G9BXC7 · checks-v2
Model Ledger MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 06:44 UTC for model-ledger 0.7.13. 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, 06:44 UTC
- Commit
- —
- Package
- pypi · 0.7.13
- Methodology
- checks-v2
Origin
30 / 30 points- PassSource repository linked and reachable10 pts
block/model-ledger is public and reachable
github.com/block/model-ledger ↗ - PassPackage names this repository as its source5 pts
model-ledger names block/model-ledger as source
pypi.org/project/model-ledger/ ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for model-ledger
pypi.org/project/model-ledger/ ↗ - Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-09-17
github.com/block/model-ledger ↗ - 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 model-ledger
- PassNo critical advisory in the package or its dependencies15 pts
12 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 model-ledger 0.7.13; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.