Report 01M7DEH8PKXQADTNR6247SN51R · checks-v2
Sequant 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.
7 of 11 checks ran · 0 high findings · not a security audit
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 --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - OpenSSF Scorecard up to +6 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- PassSource repository linked and reachable10 pts
sequant-io/sequant is public and reachable
github.com/sequant-io/sequant ↗ - PassPackage names this repository as its source5 pts
sequant name sequant-io/sequant as source
npmjs.com/package/sequant ↗ - 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
14 / 20 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-12
github.com/sequant-io/sequant ↗ - PartialOpenSSF Scorecard9 / 15 pts
OpenSSF Scorecard 5.9 / 10; weakest: Code-Review 0, Token-Permissions 0, CII-Best-Practices 0
scorecard.dev/viewer/?uri=github.com/sequant-io/sequant ↗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
10 / 10 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from sequant
- 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
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.