Report 01M7AVH17XEYPQN5A9R1JPQHVY · checks-v2

WebLoom MCP server: automated checks

What HostedMCP checked on 13 Nov 2026, 16:23 UTC. Every result links to the public source it came from, so you can check it yourself.

Not verified

67/100

5 of 11 checks ran · 0 high findings · not a security audit

Checked: 13 Nov 2026, 16:23 UTC
Commit: —
Package: https://github.com/webloomhq/engine/releases/download/v0.3.31/webloom-0.3.31.mcpb · 0.3.31
Methodology: checks-v2

What to fix for a higher score

One check can earn more points. The next scan runs within a week, or right after the repository changes.

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 / 15 points

Source repository linked and reachable10 pts
webloomhq/engine is public and reachable
github.com/webloomhq/engine ↗
Pass
Package names this repository as its source5 pts
Not checked
Build provenance (Sigstore attestation)10 pts
Not checked
Open source license (OSI)5 pts
MIT
spdx.org/licenses/MIT.html ↗
Pass

Practices

5 / 5 points

Commit or release in the last year5 pts
Last commit or release 2026-10-29
github.com/webloomhq/engine ↗
Pass
OpenSSF 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.
Not checked

Supply chain

not checked

Package name not close to a popular package10 pts
Not checked
No critical advisory in the package or its dependencies15 pts
Not checked

Tool safety

20 / 20 points

No hidden instructions to the model15 pts
1 tool description and the README read; no override phrases, credential paths or hidden characters
Pass
Destructive tools are labelled5 pts
No tool named like delete, drop or exec
Pass

Endpoint

not checked

Remote endpoint answers the MCP handshake5 pts
Not checked

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.

What to fix for a higher score

One check can earn more points. The next scan runs within a week, or right after the repository changes.

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.