Report 01M7BK0YPG6H83MD8G5D0VN8HD · checks-v2

Usage Planner MCP server: automated checks

What HostedMCP checked on 13 Nov 2026, 23:14 UTC. Every result links to the public source it came from, so you can check it yourself.

Passed HostedMCP checks

100/100

7 of 11 checks ran · 0 high findings · not a security audit

Checked: 13 Nov 2026, 23:14 UTC
Commit: —
Package: usage-planner · 0.2.7
Methodology: checks-v2

What to fix for a higher score

2 checks can earn more points. The next scan runs within a week, or right after the repository changes.

Build provenance (Sigstore attestation) up to +10 pts
Publish with build provenance: npm publish --provenance from GitHub Actions with id-token: write, or PyPI Trusted Publishing, which adds attestations.
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

20 / 20 points

Source repository linked and reachable10 pts
itsodeleo/usage-planner is public and reachable
github.com/itsodeleo/usage-planner ↗
Pass
Package names this repository as its source5 pts
usage-planner name itsodeleo/usage-planner as source
npmjs.com/package/usage-planner ↗
Pass
Build provenance (Sigstore attestation)10 pts
No build attestation published for this release
How to fix: Publish with build provenance: npm publish --provenance from GitHub Actions with id-token: write, or PyPI Trusted Publishing, which adds attestations.
Not checked
Open source license (OSI)5 pts
MIT
spdx.org/licenses/MIT.html ↗
Pass

Practices

5 / 5 points

Commit or release in the last year5 pts
Last commit or release 2026-10-29
github.com/itsodeleo/usage-planner ↗
Pass
OpenSSF 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.
Not checked

Supply chain

25 / 25 points

Package name not close to a popular package10 pts
No popular package one edit away from usage-planner
Pass
No critical advisory in the package or its dependencies15 pts
1 resolved dependencies checked; no critical advisory
osv.dev ↗
Pass

Tool safety

15 / 15 points

No hidden instructions to the model15 pts
0 tool descriptions and the README read; no override phrases, credential paths or hidden characters
Pass
Destructive tools are labelled5 pts
Not checked

Endpoint

not checked

Remote endpoint answers the MCP handshake5 pts
Not checked

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.

What to fix for a higher score

2 checks can earn more points. The next scan runs within a week, or right after the repository changes.

Build provenance (Sigstore attestation) up to +10 pts

Publish with build provenance: npm publish --provenance from GitHub Actions with id-token: write, or PyPI Trusted Publishing, which adds attestations.

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.