L
laaielichter/Gulliver
Test on tiny data before you run on giant data.
★ 2·更新 2026-11-18
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 2 ★ · laaielichter/Gulliver · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 2 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
laaielichter/Gulliver;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
Gulliver
以下摘录自该仓库的 README(片段)
Test on tiny data before you run on giant data.
An open-source MCP server and CLI that gives AI agents a dress rehearsal for SQL: estimate the cost, fix the slow parts, rehearse on 1% → 3% → 10% of the data, predict what 100% will do, and only run the full query inside a budget.
Website ·
Quick start ·
Install ·
Auto-fix ·
Guards ·
CI ·
Compare ·
FAQ ·
Roadmap
Works with Claude Code , Codex , Cursor , Gemini CLI , Claude Desktop, VS Code, Windsurf and any MCP client, on DuckDB , Postgres , BigQuery and Snowflake .
> New in 0.4.0: data quality checks you define once in gulliver.toml and run in CI with
> gulliver check --all, gulliver lint --baseline so an existing repo only sees new findings, gulliver prune,
> gulliver calibration, gulliver receipt --list, column-level gulliver diff, lint rules GV016-GV018, and
> refusal of bad budgets, unknown config keys and out-of-range flags instead of silently misreading them. See the
> changelog.
> In 0.3.0: a read-only gate that also blocks side-effect functions, SQL hidden in strings and file
> access, with DuckDB sandboxed in the engine. A result guard for personal data and prompt injection in rows. A
> runaway guard for loops and per-agent budgets. Lint for CI (SARIF, pre-commit), gulliver fix --verify,
> gulliver top, and gulliver review with a GitHub Action. One breaking change in 0.3.0: DuckDB can no
> longer read files outside the database folder and the current folder unless you allow them
> (details).
A real recording of the CLI on the demo database (script: docs/demo.sh).
> In Gulliver's Travels, Gulliver visits Lilliput, a land of tiny people, and Brobdingnag, a land of giants.
> Gulliver does the same with your data: it tries your query in Lilliput first, and only walks into Brobdingnag
> when it knows what will happen there.
## Why
Agents write SQL that works on a small table and breaks on a big one. They do not know that events has
5 billion rows, that a join multiplies rows, or that a forgotten partition filter scans every day since 2019.
Benchmarks score agents on is the answer right, never on what did it cost or does it still work at 100x.
One unlucky query can burn a monthly budget.
Gulliver sits between the agent and the warehouse:
| Step | Tool | What happens |
| 1 | gulliver_inspect | Which tables are big? Rows, bytes, partitions, columns. Metadata only, free. |
| 2 | gulliver_preflight | Bytes, rows and money before running, plus scale lint (15 rules), the read-only gate and the budget gate. When a safe rewrite exists, the answer already contains the fixed SQL (autofix). |
| 3 | gulliver_rehearse | Runs the query on 1%, 3% and 10% samples, fits a growth curve and predicts the full run with a confidence range. Catches joins that multiply rows. |
| 4 | gulliver_run | Runs the full query only inside the budget. Otherwise answers needs_rehearsal or needs_approval. The rows come back marked as untrusted data, with secrets masked and personal data flagged. |
| 5 | gulliver_receipt | Markdown proof for the human: what was estimated, rehearsed, approved and run, and predicted vs actual. |
Every answer has a status and a next_step, so even small models know what to do next.
An open-source MCP server and CLI that gives AI agents a dress rehearsal for SQL: estimate the cost, fix the slow parts, rehearse on 1% → 3% → 10% of the data, predict what 100% will do, and only run the full query inside a budget.
Website ·
Quick start ·
Install ·
Auto-fix ·
Guards ·
CI ·
Compare ·
FAQ ·
Roadmap
Works with Claude Code , Codex , Cursor , Gemini CLI , Claude Desktop, VS Code, Windsurf and any MCP client, on DuckDB , Postgres , BigQuery and Snowflake .
> New in 0.4.0: data quality checks you define once in gulliver.toml and run in CI with
> gulliver check --all, gulliver lint --baseline so an existing repo only sees new findings, gulliver prune,
> gulliver calibration, gulliver receipt --list, column-level gulliver diff, lint rules GV016-GV018, and
> refusal of bad budgets, unknown config keys and out-of-range flags instead of silently misreading them. See the
> changelog.
> In 0.3.0: a read-only gate that also blocks side-effect functions, SQL hidden in strings and file
> access, with DuckDB sandboxed in the engine. A result guard for personal data and prompt injection in rows. A
> runaway guard for loops and per-agent budgets. Lint for CI (SARIF, pre-commit), gulliver fix --verify,
> gulliver top, and gulliver review with a GitHub Action. One breaking change in 0.3.0: DuckDB can no
> longer read files outside the database folder and the current folder unless you allow them
> (details).
A real recording of the CLI on the demo database (script: docs/demo.sh).
> In Gulliver's Travels, Gulliver visits Lilliput, a land of tiny people, and Brobdingnag, a land of giants.
> Gulliver does the same with your data: it tries your query in Lilliput first, and only walks into Brobdingnag
> when it knows what will happen there.
## Why
Agents write SQL that works on a small table and breaks on a big one. They do not know that events has
5 billion rows, that a join multiplies rows, or that a forgotten partition filter scans every day since 2019.
Benchmarks score agents on is the answer right, never on what did it cost or does it still work at 100x.
One unlucky query can burn a monthly budget.
Gulliver sits between the agent and the warehouse:
| Step | Tool | What happens |
| 1 | gulliver_inspect | Which tables are big? Rows, bytes, partitions, columns. Metadata only, free. |
| 2 | gulliver_preflight | Bytes, rows and money before running, plus scale lint (15 rules), the read-only gate and the budget gate. When a safe rewrite exists, the answer already contains the fixed SQL (autofix). |
| 3 | gulliver_rehearse | Runs the query on 1%, 3% and 10% samples, fits a growth curve and predicts the full run with a confidence range. Catches joins that multiply rows. |
| 4 | gulliver_run | Runs the full query only inside the budget. Otherwise answers needs_rehearsal or needs_approval. The rows come back marked as untrusted data, with secrets masked and personal data flagged. |
| 5 | gulliver_receipt | Markdown proof for the human: what was estimated, rehearsed, approved and run, and predicted vs actual. |
Every answer has a status and a next_step, so even small models know what to do next.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/laaielichter-gulliver/)
- 来源
- awesome · https://github.com/laaielichter/Gulliver
- 按领域浏览
- MCP 服务
- Traction
- 2 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。