io.github.yiminspace/quarry
PYPI · QUARRY-DB
Safety-railed database access: Postgres, MySQL, SQLite, Redis. Read-only by default.
Available components
Last scanned (19 hours ago)
Scores higher than 74% 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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to yiminspace/quarry). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 350 tokens (~58/item across 6 items; 6 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
- 13% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "exec_sql" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 13 functional
- First check of Schema quality: good functional
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Oct 26 48
First indexed and scored.
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 16 Oct 2026 · Analysed pypi/quarry-db@1.8.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 | yiminspace/quarry |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/yiminspace/quarry/.github/workflows/release.yml@refs/tags/v1.8.0 |
| Rekor log index | 3229262792 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f0a1793190ed68b5e52a057f82830002d51c59f6f025fbf740a35bae94c29044 |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
| build_hook | unreviewed | hatch_build.py,tool.hatch.build.targets.wheel.hooks.custom |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
describe_table ~40
Column names, types and nullability for one table.
| Name | Type | Req | Description |
|---|---|---|---|
| db | string | yes | – |
| env | string | – | – |
| table | string | yes | – |
No output schema declared.
No examples provided.
exec_sql ~135
Execute SQL (or a redis command) against a database and get a structured result {columns, rows, rowCount, truncated, elapsedMs}. READ-ONLY by default: writes/DDL fail with code 8 unless you pass write=true AND the server was started with --write; a configured production connection additionally requires confirm_prod=true. SELECTs without LIMIT get an automatic LIMIT (max_rows, default 500).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_prod | boolean | – | – |
| db | string | yes | – |
| env | string | – | – |
| max_rows | integer | – | – |
| sql | string | yes | – |
| write | boolean | – | – |
No output schema declared.
No examples provided.
list_connections ~43
List all configured database connections, grouped into project folders and env-sets (same logical db across dev/prod/...). Start here to learn which `db` keys exist.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_saved_queries ~24
List the workspace's saved named queries (name, target db, params).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tables ~52
List tables of a database (or keys for a redis connection).
| Name | Type | Req | Description |
|---|---|---|---|
| db | string | yes | logical db or connection key |
| env | string | – | env-set member (dev/prod/...); defaults to dev |
No output schema declared.
No examples provided.
run_saved_query ~56
Run a saved named query by name, with `params` as {name: value}.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | – | – |
| max_rows | integer | – | – |
| name | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.yiminspace/quarry MCP server?
io.github.yiminspace/quarry runs locally as a PyPI package, launched with uvx quarry-db. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · quarry-db
claude mcp add yiminspace-quarry -- uvx quarry-db
What is the io.github.yiminspace/quarry MCP server?
io.github.yiminspace/quarry is an MCP server listed in the public MCP registry as io.github.yiminspace/quarry. Safety-railed database access: Postgres, MySQL, SQLite, Redis. Read-only by default. This page covers its PyPI package (quarry-db).
Is the io.github.yiminspace/quarry MCP server safe to use?
io.github.yiminspace/quarry scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 io.github.yiminspace/quarry MCP server expose?
io.github.yiminspace/quarry exposes 6 tools: list_connections, list_tables, describe_table, exec_sql, list_saved_queries, run_saved_query. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Is the io.github.yiminspace/quarry MCP server still maintained?
io.github.yiminspace/quarry is still listed as active in the MCP registry. We last reached this channel on 16 October 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 io.github.yiminspace/quarry MCP server under?
io.github.yiminspace/quarry declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.