io.github.Wangggym/quarry
PYPI · QUARRY-DB · SCANNED SEP 20
Safety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default.
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency23
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 349 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
How do I install the io.github.Wangggym/quarry MCP server?
io.github.Wangggym/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 wangggym-quarry -- uvx quarry-db
{
"mcpServers": {
"wangggym-quarry": {
"command": "uvx",
"args": [
"quarry-db"
]
}
}
} {
"servers": {
"wangggym-quarry": {
"command": "uvx",
"args": [
"quarry-db"
]
}
}
} codex mcp add wangggym-quarry -- uvx quarry-db
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wangggym-quarry": {
"type": "local",
"command": [
"uvx",
"quarry-db"
],
"enabled": true
}
}
} openclaw mcp add wangggym-quarry --command uvx --arg quarry-db
mcp_servers:
wangggym-quarry:
command: "uvx"
args: ["quarry-db"] {
"McpServers": {
"wangggym-quarry": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"quarry-db"
]
}
}
} assistant mcp add wangggym-quarry -t stdio -c uvx -a quarry-db
{
"mcpServers": {
"wangggym-quarry": {
"command": "uvx",
"args": [
"quarry-db"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.83 functional
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 20 Sept 2026 · Analysed pypi/quarry-db@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 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 ~134
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 prod env 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.
What is the io.github.Wangggym/quarry MCP server?
io.github.Wangggym/quarry is an MCP server listed in the public MCP registry as io.github.Wangggym/quarry. Safety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default. This page covers its PyPI package (quarry-db).
Is the io.github.Wangggym/quarry MCP server safe to use?
io.github.Wangggym/quarry scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.Wangggym/quarry MCP server expose?
io.github.Wangggym/quarry exposes 6 tools: list_connections, list_tables, describe_table, exec_sql, list_saved_queries, run_saved_query. Their descriptions and schemas cost roughly 349 tokens of context every time the server is loaded.
Is the io.github.Wangggym/quarry MCP server still maintained?
io.github.Wangggym/quarry is still listed as active in the MCP registry. We last reached this channel on 20 September 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.Wangggym/quarry MCP server under?
io.github.Wangggym/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.