J
Jackxiaozhiren/datasentry
Find bad data before your users do.
★ 2·updated 2026-11-18
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
- 2 ★ · Jackxiaozhiren/datasentry · 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 · 2 ★ · 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
Jackxiaozhiren/datasentry;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 →
DataSentry
Excerpted from the repository README (abridged)
Find bad data before your users do.
Automatic data-quality discovery, evidence-backed explanations, and safe reversible repair.
Local-first. Deterministic by default. AI optional.
Live demo ·
30-second start ·
Use cases ·
FAQ ·
PyPI ·
Examples ·
MCP setup ·
Contribute
> 中文导读:DataSentry 会先自动发现数据质量问题,再给出样本、比例、置信度等证据。修复采用 propose → preview → apply to a copy → verify → rollback 的保守流程。检测与评分不依赖 LLM,AI 只作为可选辅助,数据可以完全留在本机。
## Try it in 30 seconds
Install the current PyPI release and run the zero-config product tour:
bash
pip install --upgrade datasentry-ai
datasentry demo
datasentry-demo is also available as a direct console alias.
The demo generates synthetic dirty data, runs the built-in detectors, exports JSON + HTML reports, applies one safe repair to a copy, re-scans the repaired copy, and prints a rollback command. It needs no dataset, cloud service, API key, or LLM.
text
synthetic dirty CSV
deterministic detectors
evidence-backed issues + quality score
preview → repaired copy
re-scan → verify new/persistent issues
Prefer scanning your own data immediately?
bash
curl -L https://raw.githubusercontent.com/Jackxiaozhiren/datasentry/main/demo-data/orders.csv -o orders.csv
datasentry scan orders.csv
datasentry issues list --severity high
Or launch the interactive interfaces:
bash
datasentry # terminal UI
datasentry-server # Web UI + REST API at http://localhost:8000/ui/
## Start with your problem
| If you need to... | Start here |
| Find suspicious data before you know every rule | datasentry scan data.csv |
| See the full discovery → repair → verify loop | datasentry demo |
| Block severe data issues in CI | docs/GITHUB_ACTIONS.md |
| Add quality gates to dbt / Airflow | examples/integrations/ |
| Inspect and repair issues without overwriting the source | Safe repair |
| Give AI agents deterministic data-quality tools | docs/MCP.md |
The default path is intentionally low-commitment: scan first, inspect evidence, then decide whether a finding deserves a permanent rule or a repair.
## Why DataSentry exists
Most data-quality tools are excellent once you already know the expectations, checks, or contracts you want to enforce. Real incidents often start one step earlier: you do not yet know what is wrong.
DataSentry is built around the complete remediation loop:
text
Find → Explain → Fix safely → Verify
Find — discover common quality problems without writing every rule first.
Explain — attach samples, affected counts/ratios, detector evidence, and confidence.
Fix safely — preview changes and apply repairs to a copy instead of mutating the source.
Verify — re-scan the repaired copy and surface persistent or newly introduced issues.
DataSentry fits best when you are looking at data you do not fully trust yet, want evidence before codifying checks, or need a conservative remediation path. It complements expectation- and contract-driven tools rather than requiring you to replace them.
## What it catches automatically
DataSentry ships with a registry of deterministic detectors covering common failure modes such as:
missing and placeholder values;
invalid emails, URLs, dates, and encodings;
duplicate identifiers and uniqueness violations;
Automatic data-quality discovery, evidence-backed explanations, and safe reversible repair.
Local-first. Deterministic by default. AI optional.
Live demo ·
30-second start ·
Use cases ·
FAQ ·
PyPI ·
Examples ·
MCP setup ·
Contribute
> 中文导读:DataSentry 会先自动发现数据质量问题,再给出样本、比例、置信度等证据。修复采用 propose → preview → apply to a copy → verify → rollback 的保守流程。检测与评分不依赖 LLM,AI 只作为可选辅助,数据可以完全留在本机。
## Try it in 30 seconds
Install the current PyPI release and run the zero-config product tour:
bash
pip install --upgrade datasentry-ai
datasentry demo
datasentry-demo is also available as a direct console alias.
The demo generates synthetic dirty data, runs the built-in detectors, exports JSON + HTML reports, applies one safe repair to a copy, re-scans the repaired copy, and prints a rollback command. It needs no dataset, cloud service, API key, or LLM.
text
synthetic dirty CSV
deterministic detectors
evidence-backed issues + quality score
preview → repaired copy
re-scan → verify new/persistent issues
Prefer scanning your own data immediately?
bash
curl -L https://raw.githubusercontent.com/Jackxiaozhiren/datasentry/main/demo-data/orders.csv -o orders.csv
datasentry scan orders.csv
datasentry issues list --severity high
Or launch the interactive interfaces:
bash
datasentry # terminal UI
datasentry-server # Web UI + REST API at http://localhost:8000/ui/
## Start with your problem
| If you need to... | Start here |
| Find suspicious data before you know every rule | datasentry scan data.csv |
| See the full discovery → repair → verify loop | datasentry demo |
| Block severe data issues in CI | docs/GITHUB_ACTIONS.md |
| Add quality gates to dbt / Airflow | examples/integrations/ |
| Inspect and repair issues without overwriting the source | Safe repair |
| Give AI agents deterministic data-quality tools | docs/MCP.md |
The default path is intentionally low-commitment: scan first, inspect evidence, then decide whether a finding deserves a permanent rule or a repair.
## Why DataSentry exists
Most data-quality tools are excellent once you already know the expectations, checks, or contracts you want to enforce. Real incidents often start one step earlier: you do not yet know what is wrong.
DataSentry is built around the complete remediation loop:
text
Find → Explain → Fix safely → Verify
Find — discover common quality problems without writing every rule first.
Explain — attach samples, affected counts/ratios, detector evidence, and confidence.
Fix safely — preview changes and apply repairs to a copy instead of mutating the source.
Verify — re-scan the repaired copy and surface persistent or newly introduced issues.
DataSentry fits best when you are looking at data you do not fully trust yet, want evidence before codifying checks, or need a conservative remediation path. It complements expectation- and contract-driven tools rather than requiring you to replace them.
## What it catches automatically
DataSentry ships with a registry of deterministic detectors covering common failure modes such as:
missing and placeholder values;
invalid emails, URLs, dates, and encodings;
duplicate identifiers and uniqueness violations;
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/jackxiaozhiren-datasentry/)
- Source
- awesome · https://github.com/Jackxiaozhiren/datasentry
- Browse by field
- MCP servers
- Traction
- 2 ★
- 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.