Report 01M7D1YDDPRM4C6RBE5DVYBFM6 · checks-v2
Code Fundi MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 12:54 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
- 14 Nov 2026, 12:54 UTC
- Commit
- —
- Package
- @codefundi/code-fundi-mcp · 0.1.4
- 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
code-fundi/code-fundi-mcp is public and reachable
github.com/code-fundi/code-fundi-mcp ↗ - PassPackage names this repository as its source5 pts
@codefundi/code-fundi-mcp name code-fundi/code-fundi-mcp as source
npmjs.com/package/@codefundi/code-fundi-mcp ↗ - 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-10-07
github.com/code-fundi/code-fundi-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
25 / 25 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from @codefundi/code-fundi-mcp
- PassNo critical advisory in the package or its dependencies15 pts
158 resolved dependencies checked; no critical advisory
osv.dev ↗
Tool safety
20 / 20 points- PassNo hidden instructions to the model15 pts
27 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
- 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.