REPORT 01M7CG6SB2H3PTWWGF4WP0ANT3 · checks-v2
Swarmcode MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 07:44 UTC. Every result links to the public source it came from, so you can check it yourself.
Not verified
67/100
5 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 07:44 UTC
- Commit
- —
- Package
- hosted endpoint
- Methodology
- checks-v2
Origin
15 / 15 points- PassSource repository linked and reachable10 pts
spranab/swarmcode is public and reachable
github.com/spranab/swarmcode ↗ - Not checkedPackage names this repository as its source5 pts
- Not checkedBuild provenance (Sigstore attestation)10 pts
- Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-10-31
github.com/spranab/swarmcode ↗ - Not checkedOpenSSF Scorecard15 pts
Supply chain
not checked- Not checkedPackage name not close to a popular package10 pts
- Not checkedNo critical advisory in the package or its dependencies15 pts
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
5 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; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.