Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

StackQL MCP Server

MCPB · LINUX-X64 · 8 COMPONENTS

SQL-native query and provisioning engine for cloud infrastructure, served over MCP.

0 this week 53 Trust /100

Last scanned (19 hours ago)

Scores higher than 84% of MCPB servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 16 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5445 tokens (~286/item across 19 items; 15 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 41% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed mcpb/https://github.com/stackql/stackql/releases/download/v1.0.888/stackql-mcp-linux-x64.mcpb@1.0.888

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 15 exposed · ~1,575 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
describe_method ~147

Full I/O contract for one method: every input with its param_type (input_required params become exact-match WHERE predicates; input_optional ones may be added) and every output field, which are the columns a SELECT or RETURNING can reference. Call it after list_methods and before the first query against a method; there is no resource-level equivalent because each method returns its own shape. Requires provider, service, resource, method.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
methodstring––
providerstring––
resourcestring––
row_limitinteger––
servicestring––
NameTypeReqDescription
rowsnull|arrayyes–

No examples provided.

list_methods ~124

Access methods for a resource with their SQL verb and required params. Pick the method whose verb matches the intent and whose required params you can supply, then describe_method it. Call when composing SQL from scratch against an unfamiliar resource; not needed when executing a vetted query library template. Requires provider, service, resource.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
methodstring––
providerstring––
resourcestring––
row_limitinteger––
servicestring––
NameTypeReqDescription
rowsnull|arrayyes–

No examples provided.

list_providers ~24

Available cloud/SaaS providers (top of the hierarchy). No inputs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
rowsnull|arrayyes–

No examples provided.

list_registry ~75

Providers (and their versions) available in the configured registry. Distinct from list_providers, which lists only providers already pulled. Optional provider arg lists versions for that provider.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
providerstring––
versionstring––
NameTypeReqDescription
rowsnull|arrayyes–

No examples provided.

list_resources ~73

Resources under a provider.service. Requires provider and service.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
methodstring––
providerstring––
resourcestring––
row_limitinteger––
servicestring––
NameTypeReqDescription
rowsnull|arrayyes–

No examples provided.

list_services ~70

Services under a provider. Requires provider.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
methodstring––
providerstring––
resourcestring––
row_limitinteger––
servicestring––
NameTypeReqDescription
rowsnull|arrayyes–

No examples provided.

pull_provider ~81

Install a single provider from the registry into the local approot cache. Requires provider; version is optional (latest published is pulled when empty). Writes only local cache state; no cloud control/data plane effect.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
providerstring––
versionstring––

Structured output declared, but exposes no named fields.

No examples provided.

query_library_get ~130

Retrieve a query library entry by id. Without params: returns the raw template, param declarations and notes (adapt from it when no exact match exists). With params: the server validates values and returns rendered SQL plus which tool to execute it with (run_select_query or run_mutation_query). Read-only, no credentials.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
idstringyesquery id from search results, eg aws/ec2/regions-enabled
paramsobject–parameter values; when supplied the server validates and returns rendered SQL
NameTypeReqDescription
authnull|array–env vars the template's providers need resolved
costnull|object––
descriptionstring––
doc_urlstring––
errorsnull|array––
idstringyes–
missing_paramsnull|array––
mutationbooleanyes–
next_toolstringyesrun_select_query, run_mutation_query or run_lifecycle_operation
notesstring––
outputsnull|array––
paramsnull|array––
permissionsnull|array–provider-native permissions or actions required to execute the template (eg iam:ListUsers)
relatednull|array–related library entry ids
renderedbooleanyes–
source_tierstring––
source_urlstring–citation: URL or embedded path the document was loaded from
sqlstring–rendered SQL, present when rendered and valid
staleboolean––
templatestring–raw template with {{param}} placeholders
titlestring––
unknown_paramsnull|array––
validbooleanyes–
verbstring–select, mutation or lifecycle

No examples provided.

query_library_search ~154

Search the curated StackQL query library by natural-language intent. Returns ranked template ids. Consult before composing SQL from scratch; follow with query_library_get, which validates params and surfaces any the index omits. Read-only, no credentials.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
include_mutationsboolean––
intentstringyesnatural language description of what the user wants
limitinteger–max hits, default 5, max 20
providerstring–filter by provider, eg aws
servicestring–filter by service, eg ec2
tagsnull|array–filter by tags
NameTypeReqDescription
guidancestring–authoring guidance returned on the miss path
hitsnull|arrayyes–
missbooleanyestrue when no hit cleared the score threshold
source_tierstring–primary, fallback or snapshot
source_urlstring–citation: URL or embedded path the catalogue was loaded from
staleboolean–true when served from cache or snapshot after fetch failure

No examples provided.

reload_credentials ~167

Live-reload provider credentials: re-sources the server's configured env file into the process environment, invalidates cached auth contexts, and reports resolution status for every installed provider (optional provider arg filters the report; changed field flags values that differ from before). Never returns secret values. Credentials resolve automatically at query time - never call this at session start or before queries. Call only after a query fails with a credential resolution error (fix the env file first, then reload, then retry) or when the user says credentials have been rotated or changed. If the report shows changed: false after a failure, the file was not updated - ask the user rather than retrying.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
providerstring––
NameTypeReqDescription
env_filestring–configured dotenv file path, empty when none configured
env_file_sourcedbooleanyestrue when the env file was found and sourced on this call
providersnull|arrayyes–
sourced_varsnull|array–names of environment variables set from the env file (values are never returned)

No examples provided.

run_lifecycle_operation ~112

Execute a stackql EXEC lifecycle operation (eg EXEC aws.ec2.instances.start_instances ...). Real cloud side effects. Discover available operations and required params via list_methods and describe_method. Returns {messages, timestamp}. Gated by server mode.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
row_limitinteger––
sourcestring–query library id when the SQL originated from a library entry; attribution only
sqlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

run_mutation_query ~122

Execute INSERT/UPDATE/REPLACE/DELETE against the provider. Real side effects. Returns {messages, timestamp}. Gated by server mode. Consult query_library_search for a vetted template before composing SQL from scratch; when the SQL came from a library entry, pass its id as source.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
row_limitinteger––
sourcestring–query library id when the SQL originated from a library entry; attribution only
sqlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

run_select_query ~116

Execute a SELECT. Returns {rows}. Reads only; INSERT, UPDATE, DELETE and EXEC are refused in every mode. Consult query_library_search for a vetted template before composing SQL from scratch; when the SQL came from a library entry, pass its id as source.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
row_limitinteger––
sourcestring–query library id when the SQL originated from a library entry; attribution only
sqlstringyes–
NameTypeReqDescription
rowsnull|arrayyes–

No examples provided.

server_info ~59

Get server identity and runtime: stackql version, backing SQL engine, provider registry location, mode, read-only flag. Call on demand - eg to diagnose a refused/gated operation or check version-specific behavior. Not needed at session start or before queries.

Input schema present but exposes no named parameters.

NameTypeReqDescription
build_datestring––
commitstring––
is_read_onlybooleanyes–
modestring––
platformstring––
provider_registrystring––
sql_backendstring––
transportstring––
versionstring––

No examples provided.

validate_select_query ~121

Parse and plan a SELECT without executing; the provider's credentials must still resolve, as for execution. Returns {valid, errors}. Use when iterating on syntax or plan errors, or pre-flighting complex/expensive queries - don't validate routinely; run_select_query surfaces the same errors.

NameTypeReqDescription
formatstring–text content render format: markdown (default) or json
row_limitinteger––
sourcestring–query library id when the SQL originated from a library entry; attribution only
sqlstringyes–
NameTypeReqDescription
errorsnull|array––
validbooleanyes–

No examples provided.

Install

How do I install the StackQL MCP Server server?

StackQL MCP Server ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 466159686797ee15955defbb66c0fe5fb140b95959e3699d392696566b8600a7; the commands to do that are on this page. If it does not match, do not open it.

mcpb · linux-x64

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

466159686797ee15955defbb66c0fe5fb140b95959e3699d392696566b8600a7

macOS / Linux

echo "466159686797ee15955defbb66c0fe5fb140b95959e3699d392696566b8600a7  stackql-mcp-linux-x64.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\stackql-mcp-linux-x64.mcpb).Hash -eq "466159686797ee15955defbb66c0fe5fb140b95959e3699d392696566b8600a7"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the StackQL MCP Server server?

StackQL MCP Server is listed in the public MCP registry as io.github.stackql/stackql-mcp. SQL-native query and provisioning engine for cloud infrastructure, served over MCP. This page covers its MCPB bundle (https://github.com/stackql/stackql/releases/download/v1.0.888/stackql-mcp-linux-x64.mcpb).

Is the StackQL MCP Server server safe to use?

StackQL MCP Server scores 53 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the StackQL MCP Server server expose?

StackQL MCP Server exposes 15 tools: describe_method, list_methods, list_providers, list_registry, list_resources, and 10 more. Their descriptions and schemas cost roughly 1,575 tokens of context every time the server is loaded.

What licence is the StackQL MCP Server server under?

StackQL MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the StackQL MCP Server server?

VerifyMCP ran 12 checks on StackQL MCP Server, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about StackQL MCP Server: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.