StackQL MCP Server

Query, provision and operate Cloud, SaaS, API and Model Context Protocol (MCP) resources through a unified SQL-based fra

MCP Servers Go Grade B Listed MIT
66.7/100
Rank #280 of 1320
Compare StackQL MCP Server

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +7

Is StackQL MCP Server safe? StackQL MCP Server scores 66.7/100 (Grade B), ranked #280 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 98% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
66.3
Activity sub-score · out of 100
#137

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →

Signals refreshed 2026-09-04 23:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
898
Forks
83
Last Push
2026-09-04
today
Commits (4 wk)
14
Downloads (7d)
152
pypi
HN mentions (30d)
Open Issues
102
Rank Change
▼12
was #268

Analysis

HVTrust Dimensions vs MCP Servers

66.7 / 100 · 100.0% confidence

StackQL MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.9 / 25
1.3 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
0.8 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
16.7 / 20
4.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
10.0 / 20
3.7 above avg 6.3

Activity Inputs

66.3 / 100
StarsRepository reach
17.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
14.7 / 25
CommunityFork signal
8.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.8 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
98%
of last 100 commits verified
Binary-Artifacts 9
Branch-Protection 6
CI-Tests 10
CII-Best-Practices 0
Code-Review 5
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is StackQL MCP Server safe?

StackQL MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does StackQL MCP Server publish package provenance?
No published build provenance is currently detected for StackQL MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does StackQL MCP Server have an OpenSSF Scorecard?
StackQL MCP Server has an OpenSSF Scorecard score of 4.8/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 1 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?
98% 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
1 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

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.

Reputation Timeline

Signal history
Rank 9Listed 1HVTrust 1Grade 1Scorecard 1
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)
2026-08-10
Rank Moved
Rank dropped 20 spots (#604 → #624)
2026-08-08
Newly Listed
First tracked at rank #606

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 66.7 Grade B
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.3 · Raw JSON