REPORT 01M7C8RR58P4NGY5P4FKJCGK86 · checks-v2
Fuli MCP server: automated checks
What HostedMCP checked on 14 Nov 2026, 05:34 UTC for fuli-context. Every result links to the public source it came from, so you can check it yourself.
Passed HostedMCP checks v2
100/100
7 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 14 Nov 2026, 05:34 UTC
- Commit
- —
- Package
- npm · latest
- Methodology
- checks-v2
Origin
30 / 30 points- PassSource repository linked and reachable10 pts
jevonscode/fuli is public and reachable
github.com/jevonscode/fuli ↗ - PassPackage names this repository as its source5 pts
fuli-context names jevonscode/fuli as source
npmjs.com/package/fuli-context ↗ - PassBuild provenance (Sigstore attestation)10 pts
Sigstore attestation for fuli-context
npmjs.com/package/fuli-context/v/0.27.3#provenance ↗ - Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-11-14
github.com/jevonscode/fuli ↗ - Not checkedOpenSSF Scorecard15 pts
Supply chain
10 / 10 points- PassPackage name not close to a popular package10 pts
No popular package one edit away from fuli-context
- Not checkedNo critical advisory in the package or its dependencies15 pts
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 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.