Report 01M7DEH8PKYY81GZ1S2A29G8MZ · checks-v2
SafeGrd MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 16:34 UTC. Every result links to the public source it came from, so you can check it yourself.
5 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 16:34 UTC
- Commit
- —
- Package
- ghcr.io/safegrd/cli:0.0.29 · latest
- 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.
- Open source license (OSI) up to +5 pts
Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
- 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
10 / 15 points- PassSource repository linked and reachable10 pts
safegrd/cli is public and reachable
github.com/safegrd/cli ↗ - Not checkedPackage names this repository as its source5 pts
- Not checkedBuild provenance (Sigstore attestation)10 pts
- FindingOpen source license (OSI)5 pts
No license
How to fix: Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
Practices
5 / 5 points- Pass
- 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
not checked- Not checkedPackage name not close to a popular package10 pts
- Not checkedNo critical advisory in the package or its dependencies15 pts
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
5 / 5 points- PassRemote endpoint answers the MCP handshake5 pts
HTTPS endpoint answered 401 (sign-in required)
What these checks do not cover
- Tools are listed but never called, and the server's 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.