Report 01M7C9XCBZW8CNWCXS2V0DF7DT · checks-v2
Agentcomms MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 05:54 UTC. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks
100/100
9 of 11 checks ran · 0 high findings · not a security audit
Origin
30 / 30 points- PassSource repository linked and reachable10 pts
web3wes/agentcomms is public and reachable
github.com/web3wes/agentcomms ↗ - PassPackage names this repository as its source5 pts
agentcomms-secure name web3wes/agentcomms as source
pypi.org/project/agentcomms-secure/ ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for agentcomms-secure
pypi.org/project/agentcomms-secure/ ↗ - Pass
Practices
20 / 20 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-11
github.com/web3wes/agentcomms ↗ - PassOpenSSF Scorecard15 pts
OpenSSF Scorecard 7.0 / 10; weakest: Code-Review 0, Maintained 0, CII-Best-Practices 0
scorecard.dev/viewer/?uri=github.com/web3wes/agentcomms ↗
Supply chain
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from agentcomms-secure
- PassNo critical advisory in the package or its dependencies15 pts
4 resolved dependencies checked; no critical advisory
osv.dev ↗
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.