Report 01M7B98FN9R9G5BR8CQQMS7K9F · checks-v2
Opencode MCP server: automated checks
What HostedMCP checked on 13 Nov 2026, 20:23 UTC. Every result links to the public source it came from, so you can check it yourself.
7 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 13 Nov 2026, 20:23 UTC
- Commit
- —
- Package
- mcp-server-opencode · latest
- 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.
- Build provenance (Sigstore attestation) up to +10 pts
Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - 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
15 / 20 points- PassSource repository linked and reachable10 pts
alejandro-technology/opencode-mcp is public and reachable
github.com/alejandro-technology/opencode-mcp ↗ - PassPackage names this repository as its source5 pts
mcp-server-opencode name alejandro-technology/opencode-mcp as source
npmjs.com/package/mcp-server-opencode ↗ - Not checkedBuild provenance (Sigstore attestation)10 pts
No build attestation published for this release
How to fix: Publish with build provenance:
npm publish --provenancefrom GitHub Actions withid-token: write, or PyPI Trusted Publishing, which adds attestations. - 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-11-12
github.com/alejandro-technology/opencode-mcp ↗ - 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
10 / 10 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from mcp-server-opencode
- Not checkedNo critical advisory in the package or its dependencies15 pts
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
10 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 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.