pipeverify
Related Servers
Alternatives to pipeverify
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to compare two tables across the same or different databases and report what changed, which columns changed, and where changes concentrate, plus source/table discovery and schema description. Runs four read-only tools that take source names rather than connection strings, returning a stable JSON contract with a risk verdict.88 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables checking Postgres migration SQL against a table-size estate snapshot and safety policy before apply, returning approve/block verdicts with lock details and remediation guidance, plus tools to explain locks and list policy rules.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables static, database-free SQL health checks that return rule-based findings and verdicts, propose executable fixes, and verify rewrites are equivalent while comparing execution plans and suggesting indexes. Supports batch/file/git-diff review for CI gating, all at zero-dependency Tier0.MIT

bricksentryofficial
AlicenseAqualityBmaintenanceEnables AI agents to assess Databricks data changes before shipping by previewing writes against disposable clones, showing downstream Unity Catalog impact, returning deterministic policy verdicts, and producing rollback plans. It also supports plain-English diff explanations and safe-to-ship guidance.61Apache 2.0- AlicenseAqualityBmaintenanceZero-config data quality monitoring as MCP tools. Profiles a warehouse (Postgres, BigQuery, Snowflake, MySQL, DuckDB), detects anomalies, and gates CI — read-only with the connection resolved server-side, never via the model.8338 PyPI14MIT
- AlicenseAqualityBmaintenanceRead-only data patrol for AI agents: finds broken partitions in DuckDB, CSV or Parquet tables, verifies each proposed fix against source control totals on a copy, and escalates anything it cannot prove to a person.6145 PyPI1MIT
TDQS
Scored across 3 tools
The three tools target clearly distinct verification workflows: before/after comparison, output-vs-source checking, and config-wide project checking. The descriptions explicitly cross-reference when to use one instead of another, leaving little room for misselection.
All tool names use snake_case and begin with a clear verb, following a predictable action-oriented convention. check_against_source is slightly longer but still fits the same verb-first pattern.
Three tools is a tight, well-scoped surface for a read-only data verification server. Each tool corresponds to a distinct mode of checking, and none appears redundant or decorative.
The server covers the main verification paths: one-off before/after checks, source-vs-output checks, and full project config runs. A minor gap is that there is no explicit tool to create, inspect, or validate pipeverify.yml, though run_config reports config errors and users can manage the file outside the server.