Report 01M7BDTJPQWQ850GWCFZFBQYE4 · checks-v2

Tabularium MCP server: automated checks

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

Passed HostedMCP checks

94/100

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

Checked: 13 Nov 2026, 21:43 UTC
Commit: —
Package: tabularium-mcp · 0.5.5
Methodology: checks-v2

What to fix for a higher score

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

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

25 / 30 points

Source repository linked and reachable10 pts
sqlazy/tabularium is public and reachable
github.com/sqlazy/tabularium ↗
Pass
Package names this repository as its source5 pts
tabularium-mcp name sqlazy/tabularium as source
npmjs.com/package/tabularium-mcp ↗
Pass
Build provenance (Sigstore attestation)10 pts
Sigstore attestation for tabularium-mcp
npmjs.com/package/tabularium-mcp/v/0.5.5#provenance ↗
Pass
Open 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.
Finding

Practices

5 / 5 points

Commit or release in the last year5 pts
Last commit or release 2026-11-13
github.com/sqlazy/tabularium ↗
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

25 / 25 points

Package name not close to a popular package10 pts
No popular package one edit away from tabularium-mcp
Pass
No critical advisory in the package or its dependencies15 pts
112 resolved dependencies checked; no critical advisory
osv.dev ↗
Pass

Tool safety

20 / 20 points

No hidden instructions to the model15 pts
10 tool descriptions 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

5 / 5 points

Remote endpoint answers the MCP handshake5 pts
initialize answered with protocol 2025-06-18 in 79 ms
Pass

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

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

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.