Is StackQL MCP Server safe to use?

StackQL MCP Server has an HVTrust score of 87.1/100 (Grade A), ranked #74 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for StackQL MCP Server?

StackQL MCP Server scores 87.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.1k GitHub stars and is categorized under MCP Servers.

StackQL MCP Server

Repository

Website

Query, provision and operate Cloud, SaaS, API and Model Context Protocol (MCP) resources through a unified SQL-based framework for humans and AI agents.

MCP Servers Go Listed MIT

Is StackQL MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.2 / 10

Provenance Attested

Signed commits 100%

Last push 5d ago

Advisories None known

Compare StackQL MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: StackQL MCP Server scores 87.1/100 (Grade A), ranked #74 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.2/10; 100% of recent commits are signed; no published advisory affects its latest release (@stackql/mcp-server, stackql-mcp-server); last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How StackQL MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 6.2 to 9.0lowest checks: CII-Best-Practices 0, Pinned-Dependencies 0, Signed-Releases 0 +4.1 → 91.2 A · #4 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships StackQL MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/stackql/stackql, MIT, last pushed 2026-11-05. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Nov 3, 2026). The checks that decide who can get a change released:
- Code Review2
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 9

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Partly attested
- npm @stackql/mcp-server Source link points back to this repo Build provenance attested
- PyPI stackql-mcp-server Source link points back to this repo No build attestation
What you install today No known advisories

Latest releases checked: @stackql/mcp-server 1.0.888, stackql-mcp-server 1.0.888. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-11-05 Package provenance attestation detected
2026-08-29 OSSF Scorecard: 4.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues StackQL MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How StackQL MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks StackQL MCP Server’s 87.1.

Where the 87.1 comes from

HVTrust dimensions vs the MCP Servers average

87.1 / 100 · 100.0% confidence

StackQL MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.2 / 25

9.4 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.3 above avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.5 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

18.4 / 20

6.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

12.3 / 20

4.7 above avg 7.6

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-11-05

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-11-05

Provenance Added

Package provenance attestation detected

2026-11-05

Grade Changed

Trust grade B → A

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent View MCP Servers Report missing data

72.9

Activity sub-score · out of 100

#23

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

1.1k

Forks

Last Push

2026-11-05

5 days ago

Commits (4 wk)

Downloads (7d)

5,608

npm+docker+pypi

HN mentions (30d)

—

Open Issues

112

Rank Change

was #74

Analysis

Activity Inputs

72.9 / 100

StarsRepository reach

18.2 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

21.2 / 25

CommunityFork signal

9.1 / 20

Common questions about StackQL MCP Server

Public supply-chain signals for StackQL MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but StackQL MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

Does StackQL MCP Server publish package provenance?

Yes. StackQL MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does StackQL MCP Server have an OpenSSF Scorecard?

StackQL MCP Server has an OpenSSF Scorecard score of 6.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is StackQL MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does StackQL MCP Server use?

StackQL MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are StackQL MCP Server's commits signed?

100% of the last 100 commits to StackQL MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

StackQL MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to StackQL MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-11-05

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-11-05

Provenance Added

Package provenance attestation detected

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-24

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain StackQL MCP Server?

For maintainers

HVTrust scores StackQL MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-05

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-11-05

Provenance Added

Package provenance attestation detected

2026-11-05

Grade Changed

Trust grade B → A

2026-11-05

Rank Moved

Rank rose 210 spots (#279 → #69)

2026-11-05

HVTrust Changed

HVTrust up 13.4pts (74.1 → 87.5)

2026-11-01

Rank Moved

Rank rose 19 spots (#305 → #286)

2026-10-09

Rank Moved

Rank dropped 13 spots (#286 → #299)

2026-10-07

Rank Moved

Rank dropped 12 spots (#273 → #285)

2026-10-06

Rank Moved

Rank rose 13 spots (#286 → #273)

2026-09-24

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-24

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-24

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-24

Rank Moved

Rank rose 64 spots (#363 → #299)

2026-09-24

HVTrust Changed

HVTrust up 3.2pts (68.5 → 71.7)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 286 spots (#649 → #363)

2026-09-23

HVTrust Changed

HVTrust up 36.2pts (32.3 → 68.5)

2026-09-22

Newly Listed

First tracked at rank #649

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-14

Rank Moved

Rank rose 41 spots (#380 → #339)

2026-09-12

Rank Moved

Rank dropped 14 spots (#360 → #374)

2026-09-05

Rank Moved

Rank dropped 66 spots (#280 → #346)

2026-09-04

Rank Moved

Rank dropped 12 spots (#268 → #280)

2026-09-03

Rank Moved

Rank dropped 16 spots (#252 → #268)

2026-08-31

Rank Moved

Rank dropped 31 spots (#226 → #257)

2026-08-29

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-29

Grade Changed

Trust grade D → B

2026-08-29

Rank Moved

Rank rose 550 spots (#783 → #233)

2026-08-29

HVTrust Changed

HVTrust up 27.0pts (39.9 → 66.9)

2026-08-28

Rank Moved

Rank dropped 29 spots (#754 → #783)

2026-08-27

Rank Moved

Rank dropped 22 spots (#732 → #754)

2026-08-26

Rank Moved

Rank dropped 97 spots (#635 → #732)

2026-08-16

Rank Moved

Rank dropped 12 spots (#621 → #633)

GitHub → Website → PyPI: stackql-mcp-server npm: @stackql/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/stackql-mcp-server.svg)](https://hvtracker.net/agents/stackql-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/stackql-mcp-server"><img src="https://hvtracker.net/badge/stackql-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

StackQL MCP Server

How StackQL MCP Server could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Partly attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How StackQL MCP Server compares in MCP Servers

Where the 87.1 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about StackQL MCP Server

AI agent surface

Maintain StackQL MCP Server?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers