J
Jackxiaozhiren/datasentry
Find bad data before your users do.
★ 2·更新 2026-11-18
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 2 ★ · Jackxiaozhiren/datasentry · 取自 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 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Jackxiaozhiren/datasentry;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
DataSentry
以下摘录自该仓库的 README(片段)
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;
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/jackxiaozhiren-datasentry/)
- 来源
- awesome · https://github.com/Jackxiaozhiren/datasentry
- 按领域浏览
- MCP 服务
- Traction
- 2 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。