sql-steward
PYPI · SQL-STEWARD
The agent never writes SQL: queries compile from a semantic layer you control, PII refused first.
Available components
Last scanned (22 hours ago)
Scores higher than 69% of PyPI servers
Category Databases
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to Pawansingh3889/sql-steward). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 108 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 548 tokens (~60/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
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.
- 4 Nov 26 +1
- Stability: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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 4 Nov 2026 · Analysed pypi/sql-steward@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Pawansingh3889/sql-steward |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Pawansingh3889/sql-steward/.github/workflows/release.yml@refs/tags/v0.4.0 |
| Rekor log index | 2194775877 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ae2150616b6a8bcdbd42913b0841df4f76a0e3d34127774a60598fd6514fdd0f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
audit_verify Audit Verify ~37
Verify the tamper-evident audit chain (agent-blackbox), if enabled. Reports whether any previously recorded call was altered after the fact.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
describe_entity Describe Entity ~56
Show one entity's fields, types and PII tags. Fields tagged with a blocked PII category are marked `blocked: true`; asking for them in get_records is refused before any query runs.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_metric Get Metric ~55
Compute a pre-approved metric, optionally grouped/filtered by allowed dimensions. The aggregation itself is fixed by the semantic layer.
| Name | Type | Req | Description |
|---|---|---|---|
| dimensions | – | – | – |
| filters | – | – | – |
| limit | – | – | – |
| metric | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_records Get Records ~112
Read rows from one entity. `filters` is a list of {field, op, value}. Operators: =, !=, <, <=, >, >=, like, in, not in, is null, is not null. Blocked-PII fields are refused before anything runs; cross-entity references without a defined join are refused as unreachable.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| fields | – | – | – |
| filters | – | – | – |
| limit | – | – | – |
| order_by | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_checks List Checks ~19
List the declared data-quality checks the layer can run.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_entities List Entities ~56
List the entities (tables) you may read, plus the available metrics. Call this first. You never write SQL -- you pass names from here to get_records / get_metric and sql-steward compiles the query for you.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_metrics List Metrics ~21
List pre-approved metrics and the dimensions/filters each one allows.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
run_checks Run Checks ~81
Run the declared data-quality checks and return a readiness summary. Each check compiles to a read-only violation count; zero violations passes. Returns a readiness score (percent of checks passing), an overall status, and a per-check breakdown. An 'error'-severity failure makes the status 'failing'; a 'warn'-severity failure makes it 'degraded'.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
semantic_search Semantic Search ~111
Vector similarity search over an entity's embedding column (pgvector). `query` is embedded locally and matched against the entity's configured embedding; the closest rows are returned (the embedding itself never is). Requires the entity to have a `search` config and a local embedding model (SQL_STEWARD_EMBED_URL). PostgreSQL-only. Same PII refusal as everything else.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| filters | – | – | – |
| k | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the sql-steward MCP server?
sql-steward runs locally as a PyPI package, launched with uvx sql-steward. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sql-steward
claude mcp add pawansingh3889-sql-steward -- uvx sql-steward
What is the sql-steward MCP server?
sql-steward is an MCP server listed in the public MCP registry as io.github.Pawansingh3889/sql-steward. The agent never writes SQL: queries compile from a semantic layer you control, PII refused first. This page covers its PyPI package (sql-steward).
Is the sql-steward MCP server safe to use?
sql-steward scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 sql-steward MCP server expose?
sql-steward exposes 9 tools: list_entities, describe_entity, list_metrics, get_records, get_metric, and 4 more. Their descriptions and schemas cost roughly 548 tokens of context every time the server is loaded.
Is the sql-steward MCP server still maintained?
sql-steward is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the sql-steward MCP server under?
sql-steward declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.