REPORT 01M7CJG11ZN43HG8M3YXYTRQ5N · checks-v2

Securityscan MCP server: automated checks

What HostedMCP checked on 14 Nov 2026, 08:24 UTC for securityscan-mcp 0.2.0. Every result links to the public source it came from, so you can check it yourself.

Passed HostedMCP checks v2

100/100

7 of 11 checks ran · 0 high findings · not a security audit

Checked: 14 Nov 2026, 08:24 UTC
Commit: —
Package: pypi · 0.2.0
Methodology: checks-v2

Origin

15 / 15 points

Source repository linked and reachable10 pts
securityscan-api/securitystack-mcp is public and reachable
github.com/securityscan-api/securitystack-mcp ↗
Pass
Package names this repository as its source5 pts
Not checked
Build provenance (Sigstore attestation)10 pts
No build attestation published for this release
Not checked
Open source license (OSI)5 pts
Apache-2.0
spdx.org/licenses/Apache-2.0.html ↗
Pass

Practices

5 / 5 points

Commit or release in the last year5 pts
Last commit or release 2026-08-30
github.com/securityscan-api/securitystack-mcp ↗
Pass
OpenSSF Scorecard15 pts
Not checked

Supply chain

25 / 25 points

Package name not close to a popular package10 pts
No popular package one edit away from securityscan-mcp
Pass
No critical advisory in the package or its dependencies15 pts
70 resolved dependencies checked; no critical advisory
osv.dev ↗
Pass

Tool safety

20 / 20 points

No hidden instructions to the model15 pts
8 tool descriptions and the README read; no override phrases, credential paths or hidden characters
Pass
Destructive tools are labelled5 pts
No tool named like delete, drop or exec
Pass

Endpoint

not checked

Remote endpoint answers the MCP handshake5 pts
Not checked

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 securityscan-mcp 0.2.0; a later release can differ.
A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.