REPORT 01M7CG6SB2BCRTWHWTFQD8Q80H · checks-v2
Sovseal Memory MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 07:44 UTC for @sovseal/mcp-server 0.3.8. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks v2
100/100
8 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 07:44 UTC
- Commit
- —
- Package
- npm · 0.3.8
- Methodology
- checks-v2
Origin
20 / 20 points- PassSource repository linked and reachable10 pts
sovseal/core is public and reachable
github.com/sovseal/core ↗ - PassPackage names this repository as its source5 pts
@sovseal/mcp-server names sovseal/core as source
npmjs.com/package/@sovseal/mcp-server ↗ - Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
- Pass
Practices
5 / 5 points- Pass
- Not checkedOpenSSF Scorecard15 pts
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from @sovseal/mcp-server
- PassNo critical advisory in the package or its dependencies15 pts
235 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
2 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 state on the date above and @sovseal/mcp-server 0.3.8; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.