Report 01M7CFMFXQVGP35Z2JQN38CKGF · checks-v2
Sequesign MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 07:34 UTC. Every result links to the public source it came from, so you can check it yourself.
9 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 07:34 UTC
- Commit
- —
- Package
- @sequesign/mcp · 0.4.1
- 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
sequesign/mcp is public and reachable
github.com/sequesign/mcp ↗ - PassPackage names this repository as its source5 pts
@sequesign/mcp name sequesign/mcp as source
npmjs.com/package/@sequesign/mcp ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for @sequesign/mcp
npmjs.com/package/@sequesign/mcp/v/0.4.1#provenance ↗ - Pass
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
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from @sequesign/mcp
- PassNo critical advisory in the package or its dependencies15 pts
102 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
8 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
- 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.