A
akshaysharma1088/dataranger
DataRanger patrols your data, fixes what it can prove, and calls you for the rest.
★ 8·更新 2026-11-19
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 8 ★ · akshaysharma1088/dataranger · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 8 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
akshaysharma1088/dataranger;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
DataRanger patrols your data, fixes what it can prove, and calls you for the res
以下摘录自该仓库的 README(片段)
A park ranger walks the trails, fixes what is safe to fix on the spot, radios in anything dangerous,
and files a report. DataRanger does the same for your tables. It finds data-quality incidents, tests every
candidate fix on a copy against the source's control totals, applies only the fixes it can prove, and keeps
wrong fixes under a rate you choose. Everything else goes to a person, with the evidence attached.
The dotted line under the name is a patrol trail: one marker per daily partition, the same marks the patrol console uses.
Most data-quality tools stop at an alert. Letting an AI agent fix data is the obvious next step, and a risky one: a wrong fix can pass every monitor you have. In the DQ-Repair benchmark, a rules engine left wrong data behind in 31% of incidents and an agent checked only by monitors in 24%. DataRanger's calibrated gate kept it under 1% while handling 59% of incidents without a person.
## The patrol loop
1. Detect. Rules and statistics find nulls, duplicates, schema drift, late partitions, broken references, unit errors and silent shifts. No LLM.
2. Diagnose. A language model answers one narrow question: what is the likely cause?
3. Propose fix. A templated fix (dedupe, backfill, quarantine, patch). The model fills in parameters only.
4. Verify. pipeverify checks the fix against source data, on a copy.
5. Gate. Proven and low risk: applied as a new version, never an overwrite. Anything else: escalated.
6. Report. Every detection, fix and decision lands on a live dashboard and an audit log.
## The patrol console
Every patrol writes one self-contained page that answers a data team's morning question: what broke, what DataRanger fixed, and what needs a person.
The trail across the top shows every daily partition on the patrol. Yellow diamonds need you, solid green markers were fixed and proven against the source, hollow ones were checked and left alone.
The queue lists incidents by what they need from you.
The evidence view shows what fired, the partition next to its source totals, and every fix DataRanger tested on a copy, with its gap to the source against the certified threshold. Above, two copies of re-sent rows disagree: keeping the first copy would leave a 0.12% gap, so DataRanger kept the latest copy, which matches exactly.
Decisions (approve, reject, roll back, reopen) are recorded in the audit log and feed the next calibration.
## Try it
Run the demo notebook in your browser to see the
summary, audit rows and interactive dashboard without installing anything locally.
bash
pip install dataranger
dataranger demo # patrol a sample table with planted problems; opens as dataranger-demo/dashboard.html
On Windows, if dataranger is "not recognized" after installing, run it as python -m dataranger instead.
On your own DuckDB tables (a fact table partitioned by date, a reference table, and the source's control totals):
bash
dataranger patrol --db warehouse.duckdb --table payments --ref-table customers \
--manifest-table control_totals --key payment_id --reference customer_id \
--date booking_date --segment channel --amount amount
Or point it straight at exported files, no database needed (.csv, .tsv or .parquet; the reader follows the extension):
and files a report. DataRanger does the same for your tables. It finds data-quality incidents, tests every
candidate fix on a copy against the source's control totals, applies only the fixes it can prove, and keeps
wrong fixes under a rate you choose. Everything else goes to a person, with the evidence attached.
The dotted line under the name is a patrol trail: one marker per daily partition, the same marks the patrol console uses.
Most data-quality tools stop at an alert. Letting an AI agent fix data is the obvious next step, and a risky one: a wrong fix can pass every monitor you have. In the DQ-Repair benchmark, a rules engine left wrong data behind in 31% of incidents and an agent checked only by monitors in 24%. DataRanger's calibrated gate kept it under 1% while handling 59% of incidents without a person.
## The patrol loop
1. Detect. Rules and statistics find nulls, duplicates, schema drift, late partitions, broken references, unit errors and silent shifts. No LLM.
2. Diagnose. A language model answers one narrow question: what is the likely cause?
3. Propose fix. A templated fix (dedupe, backfill, quarantine, patch). The model fills in parameters only.
4. Verify. pipeverify checks the fix against source data, on a copy.
5. Gate. Proven and low risk: applied as a new version, never an overwrite. Anything else: escalated.
6. Report. Every detection, fix and decision lands on a live dashboard and an audit log.
## The patrol console
Every patrol writes one self-contained page that answers a data team's morning question: what broke, what DataRanger fixed, and what needs a person.
The trail across the top shows every daily partition on the patrol. Yellow diamonds need you, solid green markers were fixed and proven against the source, hollow ones were checked and left alone.
The queue lists incidents by what they need from you.
The evidence view shows what fired, the partition next to its source totals, and every fix DataRanger tested on a copy, with its gap to the source against the certified threshold. Above, two copies of re-sent rows disagree: keeping the first copy would leave a 0.12% gap, so DataRanger kept the latest copy, which matches exactly.
Decisions (approve, reject, roll back, reopen) are recorded in the audit log and feed the next calibration.
## Try it
Run the demo notebook in your browser to see the
summary, audit rows and interactive dashboard without installing anything locally.
bash
pip install dataranger
dataranger demo # patrol a sample table with planted problems; opens as dataranger-demo/dashboard.html
On Windows, if dataranger is "not recognized" after installing, run it as python -m dataranger instead.
On your own DuckDB tables (a fact table partitioned by date, a reference table, and the source's control totals):
bash
dataranger patrol --db warehouse.duckdb --table payments --ref-table customers \
--manifest-table control_totals --key payment_id --reference customer_id \
--date booking_date --segment channel --amount amount
Or point it straight at exported files, no database needed (.csv, .tsv or .parquet; the reader follows the extension):
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/akshaysharma1088-dataranger/)
- 来源
- awesome · https://github.com/akshaysharma1088/dataranger
- 按领域浏览
- MCP 服务
- Traction
- 8 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。