Report 01M7EP0NMY8B0XT8TT83XGDWH1 · checks-v2
Conduct AI MCP server: automated checks
What HostedMCP checked on 15 Nov 2026, 04:04 UTC. Every result links to the public source it came from, so you can check it yourself.
8 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 15 Nov 2026, 04:04 UTC
- Commit
- —
- Package
- conduct-cli · 0.6.10
- Methodology
- checks-v2
What to fix for a higher score
3 checks can earn more points. The next scan runs within a week, or right after the repository changes.
- Package names this repository as its source up to +5 pts
Point the package's
repositoryfield at this repository, or list the package under the repository that publishes it. - Open source license (OSI) up to +5 pts
Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
- 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
20 / 30 points- PassSource repository linked and reachable10 pts
sseshachala/conduct-cli is public and reachable
github.com/sseshachala/conduct-cli ↗ - FindingPackage names this repository as its source5 pts
conduct-cli names https://github.com/sseshachala/conductai/issues as its source
pypi.org/project/conduct-cli/ ↗How to fix: Point the package's
repositoryfield at this repository, or list the package under the repository that publishes it. - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for conduct-cli
pypi.org/project/conduct-cli/ ↗ - FindingOpen source license (OSI)5 pts
No license
How to fix: Add a LICENSE file with an OSI-approved license such as MIT or Apache-2.0, and name it in package.json or pyproject.toml.
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-08-13
github.com/sseshachala/conduct-cli ↗ - 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 conduct-cli
- PassNo critical advisory in the package or its dependencies15 pts
6 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
- Tools are listed but never called, and the server's 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.