A
akshaysharma1088/dataranger
DataRanger patrols your data, fixes what it can prove, and calls you for the rest.
★ 8·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 8 ★ · akshaysharma1088/dataranger · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 8 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
akshaysharma1088/dataranger;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
DataRanger patrols your data, fixes what it can prove, and calls you for the res
Excerpted from the repository README (abridged)
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):
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/akshaysharma1088-dataranger/)
- Source
- awesome · https://github.com/akshaysharma1088/dataranger
- Browse by field
- MCP servers
- Traction
- 8 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.