# io.github.yiminspace/quarry (pypi · quarry-db)

Safety-railed database access: Postgres, MySQL, SQLite, Redis. Read-only by default.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- pypi · `quarry-db`: 75/100 (this document), [markdown](https://verifymcp.io/servers/yiminspace-quarry/quarry-db.md), [page](https://verifymcp.io/servers/yiminspace-quarry/quarry-db)

## Channel facts

- Registry: `pypi`
- Package: `quarry-db`
- Version: `1.8.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Supply Chain Security**: 94/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - 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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to yiminspace/quarry).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 350 tokens (~58/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add yiminspace-quarry -- uvx quarry-db
```

### Cursor

```json
{
  "mcpServers": {
    "yiminspace-quarry": {
      "command": "uvx",
      "args": [
        "quarry-db"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "yiminspace-quarry": {
      "command": "uvx",
      "args": [
        "quarry-db"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add yiminspace-quarry -- uvx quarry-db
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yiminspace-quarry": {
      "type": "local",
      "command": [
        "uvx",
        "quarry-db"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yiminspace-quarry --command uvx --arg quarry-db
```

### Hermes

```yaml
mcp_servers:
  yiminspace-quarry:
    command: "uvx"
    args: ["quarry-db"]
```

### Netclaw

```json
{
  "McpServers": {
    "yiminspace-quarry": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "quarry-db"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add yiminspace-quarry -t stdio -c uvx -a quarry-db
```

### Other

```json
{
  "mcpServers": {
    "yiminspace-quarry": {
      "command": "uvx",
      "args": [
        "quarry-db"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-15 (score 60, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-14 (score 75, +42)

- [security improvement] Injection markers: unverified → pass
- [security improvement] 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-10-13 (score 33, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-12 (score 48)

First indexed and scored.

## MCP tools (6)

### `list_connections` (~43 tokens)

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.

### `list_tables` (~52 tokens)

List tables of a database (or keys for a redis connection).

Input parameters:

- `db` (string, required): logical db or connection key
- `env` (string): env-set member (dev/prod/...); defaults to dev

### `describe_table` (~40 tokens)

Column names, types and nullability for one table.

Input parameters:

- `db` (string, required)
- `env` (string)
- `table` (string, required)

### `exec_sql` (~135 tokens)

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).

Input parameters:

- `confirm_prod` (boolean)
- `db` (string, required)
- `env` (string)
- `max_rows` (integer)
- `sql` (string, required)
- `write` (boolean)

### `list_saved_queries` (~24 tokens)

List the workspace's saved named queries (name, target db, params).

### `run_saved_query` (~56 tokens)

Run a saved named query by name, with `params` as {name: value}.

Input parameters:

- `env` (string)
- `max_rows` (integer)
- `name` (string, required)
- `params` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/yiminspace-quarry/quarry-db#diagnostics

## Score history

- 2026-10-16: 75
- 2026-10-15: 60
- 2026-10-14: 75
- 2026-10-13: 33
- 2026-10-12: 48

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/quarry-db/
- Socket report: https://socket.dev/pypi/package/quarry-db
- Repository: https://github.com/yiminspace/quarry
- Website: https://yiminspace.github.io/quarry/
- Changelog RSS feed: https://verifymcp.io/servers/yiminspace-quarry/quarry-db.xml
- Changelog JSON feed: https://verifymcp.io/servers/yiminspace-quarry/quarry-db.json
- HTML version of this page: https://verifymcp.io/servers/yiminspace-quarry/quarry-db