Report 01M7D3NB1X1DSFDYQ90J25R6B0 · checks-v2
Quantrisk MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 13:24 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, 13:24 UTC
- Commit
- —
- Package
- @quantrisk/mcp-server · 1.0.3
- Methodology
- checks-v2
What to fix for a higher score
3 checks can earn more points. The next scan runs within a week, or right after the repository changes.
- Package names this repository as its source up to +5 pts
Point the package's
repositoryfield at this repository, or list the package under the repository that publishes it. - Build provenance (Sigstore attestation) up to +10 pts
Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-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
15 / 20 points- PassSource repository linked and reachable10 pts
78degrees/mcp-server is public and reachable
github.com/78degrees/mcp-server ↗ - FindingPackage names this repository as its source5 pts
@quantrisk/mcp-server names git+https://github.com/quantrisk/mcp-server.git as its source
npmjs.com/package/@quantrisk/mcp-server ↗How to fix: Point the package's
repositoryfield at this repository, or list the package under the repository that publishes it. - Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
How to fix: Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-05-27
github.com/78degrees/mcp-server ↗ - 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 @quantrisk/mcp-server
- PassNo critical advisory in the package or its dependencies15 pts
138 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
10 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- PassDestructive tools are labelled5 pts
No tool named like delete, drop or exec
Endpoint
not checked- Not checkedRemote endpoint answers the MCP handshake5 pts
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.