Report 01M7D1YDDPBDZBQ12MA6YV7BWN · checks-v2
Jevnav MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 12:54 UTC. Every result links to the public source it came from, so you can check it yourself.
8 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 12:54 UTC
- Commit
- —
- Package
- jevnav · 0.2.2
- 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
dtduc-git/jevnav is public and reachable
github.com/dtduc-git/jevnav ↗ - PassPackage names this repository as its source5 pts
jevnav name dtduc-git/jevnav as source
pypi.org/project/jevnav/ ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for jevnav
pypi.org/project/jevnav/ ↗ - Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-09-26
github.com/dtduc-git/jevnav ↗ - 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 jevnav
- PassNo critical advisory in the package or its dependencies15 pts
36 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 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.