Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DataRanger

PYPI · DATARANGER

Read-only data patrol for AI agents: find broken partitions, prove fixes, escalate the rest.

Available components

−11 this week 68 Trust /100

Last scanned (12 hours ago)

Scores higher than 61% of PyPI servers

Category Databases

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to akshaysharma1088/dataranger). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4296 tokens (~716/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.6.0 → 0.6.3 functional
    • Package version: 0.6.0 → 0.6.2 functional
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 0
    • Package version: 0.5.4 → 0.6.0 functional
  • 17 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 +1
    • Security disclosure: fail → pass ▲ functional
  • 15 Nov 26 0
    • Package version: 0.5.1 → 0.5.4 functional
    • Package version: 0.5.1 → 0.5.3 functional
  • 14 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/dataranger@0.6.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo akshaysharma1088/dataranger
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/akshaysharma1088/dataranger/.github/workflows/release.yml@refs/tags/v0.6.3
Rekor log index 4026882089
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:2c3cfe3f3b96fa4e0a9f76e4bde00ed846837fa83c1034ceb1c52fd73de45280

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 34 packages
Packages resolved 34
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~4,168 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_incident ~311

Return the full evidence behind one incident from a patrol that has already run. Use this after a patrol tool (patrol_duckdb, patrol_files, patrol_snowflake, patrol_dbt) or run_demo, when you need to explain why a partition was auto-fixed or escalated, or to show the user what to review. A patrol records at most one incident per partition, so the folder plus the partition date identifies it. Do not call it before a patrol. Behavior: read-only. It reads audit.jsonl in out_dir and changes nothing; no network calls, returns immediately, and the result is one record of a few kilobytes. Fails with a readable error if the folder has no audit.jsonl (run a patrol first) or no incident exists for that partition. Returns one record with: partition, detectors (the problems found), decision, context (row counts and amounts for the day and for each segment, next to the source's control totals), candidates (every fix that was tried, with whether it kept the invariants and the residual gap it left) and chosen (the best-supported candidate).

NameTypeReqDescription
out_dirstringyesThe outputs.folder value returned by a patrol tool or run_demo.
partitionstringyesWhich incident: the partition date as YYYY-MM-DD, copied from an incident's 'partition' field, or 'table-level' for a problem with the whole table such as a schema change.

Structured output declared, but exposes no named fields.

No examples provided.

patrol_dbt ~1,053

Check the table behind a dbt model for data-quality incidents and say which are safe to fix. A patrol checks every daily partition of the fact table for duplicate keys, duplicate rows, missing partitions, rows that point to no reference record, null spikes, and row counts or amounts that do not match the source's control totals. For each problem it proposes a fix, tests that fix on a copy against the control totals, and decides: "auto-fixed" (proven and low risk), "no action needed" (checked, the data is right) or "escalate" (a person must decide). Use this after `dbt build` or `dbt run`, before trusting or publishing a date-partitioned model. It finds the model's table from dbt's manifest, connects the way the project's profile says (DuckDB, Snowflake and Postgres targets are supported; BigQuery is experimental), and takes the column mapping from the model's `meta: dataranger:` block unless you pass columns here. Use patrol_snowflake or patrol_duckdb for tables that are not dbt models, and patrol_files for CSV or Parquet exports. Behavior: reads target/manifest.json, dbt_project.yml and profiles.yml; it does not run dbt. It then runs three SELECT statements and nothing else, so neither the warehouse nor the dbt project is modified. On Snowflake it selects only the mapped columns for the last `days` days. The only side effect is writing four report files to out_dir: dashboard.html, audit.jsonl, incidents.csv and fixed_version.csv (the proposed corrected table, for review). Fails with a readable error if the manifest is missing (run dbt first), a model is unknown, the target type is not supported, or a mapped column does not exist. Returns the counts (incidents, auto_fixed, no_action_needed, escalate), needs_a_person (the escalated incidents), all_incidents (partition, problems, decision, proposed_fix, residual for each) and outputs (paths to the report files). Pass outputs.folder and a partition to get_incident for the full evidence behind one decision. Tell th…

NameTypeReqDescription
amount––Numeric amount column of the fact model. Omit to use meta.dataranger.amount, or amount.
category––Optional categorical column of the fact model. Omit to use meta.dataranger.category, or none.
date––Date column the fact model is partitioned by; the control totals need the same column. Omit to use meta.dataranger.date, or txn_date.
days––Read only the last N days of the fact table and control totals (today counts as day one). Use at least 30 so the checks have a baseline. Pass null to read the whole table, which can be slow and costl…
key––Primary key column of the fact model. Omit to use meta.dataranger.key, or txn_id.
manifest_model––dbt model holding the source system's control totals: one row per date and segment ('*' = whole day) with n and amount. Omit if the fact model's meta.dataranger block sets manifest_model.
modelstringyesName of the dbt fact model to check, for example fct_payments. A seed, snapshot, or a source written as source_name.table_name also works.
out_dir––Folder to write the report files into. Created if missing; report files already there are overwritten. Omit to use a new temporary folder; its path comes back in outputs.folder.
profiles_dir––Folder that holds profiles.yml. Omit to look in DBT_PROFILES_DIR, the project folder, then ~/.dbt.
project_dirstringyesPath to the dbt project folder, the one that holds dbt_project.yml. It must have been built or parsed, so target/manifest.json exists.
ref_key––Key column of the reference model. Omit to use meta.dataranger.ref_key, or customer_id.
ref_model––dbt model of the reference table that fact rows point to, for example dim_customers. Omit if the fact model's meta.dataranger block sets ref_model.
reference––Fact column that points to the reference model. Omit to use meta.dataranger.reference, or customer_id.
segment––Column that splits each day into segments, such as channel; the control totals need the same column. Omit to use meta.dataranger.segment, or channel.
target––dbt target to read from, for example prod. Omit for the profile's default target.
threshold––Gate threshold: the largest relative gap to the control totals that a verified fix may leave and still be marked auto-fixed (0.01 = 1%). Lower is stricter. Omit for the benchmark-calibrated default,…
NameTypeReqDescription
all_incidentsarrayyes–
auto_fixedintegeryes–
escalateintegeryes–
gate_thresholdnumberyes–
incidentsintegeryes–
needs_a_personarrayyes–
no_action_neededintegeryes–
notestringyes–
outputs–yes–
rows_checkedintegeryes–
tablestringyes–

No examples provided.

patrol_duckdb ~783

Check a fact table in a DuckDB database for data-quality incidents and say which are safe to fix. A patrol checks every daily partition of the fact table for duplicate keys, duplicate rows, missing partitions, rows that point to no reference record, null spikes, and row counts or amounts that do not match the source's control totals. For each problem it proposes a fix, tests that fix on a copy against the control totals, and decides: "auto-fixed" (proven and low risk), "no action needed" (checked, the data is right) or "escalate" (a person must decide). Use this before trusting, querying or building on a date-partitioned table that lives in a DuckDB database, or after a load or pipeline change to confirm the data is still right. Use patrol_files instead when the data is in CSV, TSV or Parquet files. Use run_demo to see the output on sample data. Behavior: The database is opened read-only. Your data is never modified and nothing is written back. The only side effect is writing four report files to out_dir: dashboard.html, audit.jsonl, incidents.csv, fixed_version.csv (the proposed corrected table, for review). Runs locally with no network calls; usually a few seconds, longer for tables with millions of rows. Fails with a readable error if a file, table or mapped column does not exist; the error lists the columns that are available. Returns the counts (incidents, auto_fixed, no_action_needed, escalate), needs_a_person (the escalated incidents), all_incidents (partition, problems, decision, proposed_fix, residual for each) and outputs (paths to the report files). Pass outputs.folder and a partition to get_incident for the full evidence behind one decision. Tell the user about every escalated incident.

NameTypeReqDescription
amountstring–Numeric amount column in the fact table. It is compared with the 'amount' control total.
category––Optional categorical column in the fact table. Omit if the table has none.
datestring–Date column the fact table is partitioned by, one partition per calendar day. The control totals must have a column with the same name.
dbstringyesPath to the DuckDB database file. Opened read-only.
keystring–Column in the fact table that uniquely identifies a row (the primary key).
manifest_tablestringyesTable of the source system's control totals, one row per date and segment, with columns: the date column, the segment column ('*' = whole day), n (row count) and amount (sum).
out_dir––Folder to write the report files into. Created if missing; report files already there are overwritten. Omit to use a new temporary folder; its path comes back in outputs.folder.
ref_keystring–Column in the reference table that the fact table's reference column must match.
ref_tablestringyesReference table that fact rows point to, for example customers.
referencestring–Column in the fact table that points to the reference table (the foreign key).
segmentstring–Column that splits each day into segments, for example channel or region. The control totals must have a column with the same name, where '*' means the whole day.
tablestringyesFact table to check, optionally schema-qualified, for example gold.payments.
threshold––Gate threshold: the largest relative gap to the control totals that a verified fix may leave and still be marked auto-fixed (0.01 = 1%). Lower is stricter. Omit for the benchmark-calibrated default,…
NameTypeReqDescription
all_incidentsarrayyes–
auto_fixedintegeryes–
escalateintegeryes–
gate_thresholdnumberyes–
incidentsintegeryes–
needs_a_personarrayyes–
no_action_neededintegeryes–
notestringyes–
outputs–yes–
rows_checkedintegeryes–
tablestringyes–

No examples provided.

patrol_files ~817

Check a fact table in CSV, TSV or Parquet files for data-quality incidents and say which are safe to fix. A patrol checks every daily partition of the fact table for duplicate keys, duplicate rows, missing partitions, rows that point to no reference record, null spikes, and row counts or amounts that do not match the source's control totals. For each problem it proposes a fix, tests that fix on a copy against the control totals, and decides: "auto-fixed" (proven and low risk), "no action needed" (checked, the data is right) or "escalate" (a person must decide). Use this before trusting, querying or building on a date-partitioned table exported as CSV, TSV or Parquet files, or after a load or pipeline change to confirm the data is still right. Use patrol_duckdb instead when the table lives in a DuckDB database. Use run_demo to see the output on sample data. Behavior: The three input files are only read. Your data is never modified and nothing is written back. The only side effect is writing four report files to out_dir: dashboard.html, audit.jsonl, incidents.csv, fixed_version.csv (the proposed corrected table, for review). Runs locally with no network calls; usually a few seconds, longer for tables with millions of rows. Fails with a readable error if a file, table or mapped column does not exist; the error lists the columns that are available. Returns the counts (incidents, auto_fixed, no_action_needed, escalate), needs_a_person (the escalated incidents), all_incidents (partition, problems, decision, proposed_fix, residual for each) and outputs (paths to the report files). Pass outputs.folder and a partition to get_incident for the full evidence behind one decision. Tell the user about every escalated incident.

NameTypeReqDescription
amountstring–Numeric amount column in the fact table. It is compared with the 'amount' control total.
category––Optional categorical column in the fact table. Omit if the table has none.
datestring–Date column the fact table is partitioned by, one partition per calendar day. The control totals must have a column with the same name.
facts_filestringyesPath to the fact table as .csv, .tsv, .parquet or .pq. One row per event, partitioned by a date column.
keystring–Column in the fact table that uniquely identifies a row (the primary key).
manifest_filestringyesPath to the source system's control totals as .csv, .tsv, .parquet or .pq: one row per date and segment, with the date column, the segment column ('*' = whole day), n (row count) and amount (sum).
out_dir––Folder to write the report files into. Created if missing; report files already there are overwritten. Omit to use a new temporary folder; its path comes back in outputs.folder.
ref_filestringyesPath to the reference table that fact rows point to (for example customers), as .csv, .tsv, .parquet or .pq.
ref_keystring–Column in the reference table that the fact table's reference column must match.
referencestring–Column in the fact table that points to the reference table (the foreign key).
segmentstring–Column that splits each day into segments, for example channel or region. The control totals must have a column with the same name, where '*' means the whole day.
threshold––Gate threshold: the largest relative gap to the control totals that a verified fix may leave and still be marked auto-fixed (0.01 = 1%). Lower is stricter. Omit for the benchmark-calibrated default,…
NameTypeReqDescription
all_incidentsarrayyes–
auto_fixedintegeryes–
escalateintegeryes–
gate_thresholdnumberyes–
incidentsintegeryes–
needs_a_personarrayyes–
no_action_neededintegeryes–
notestringyes–
outputs–yes–
rows_checkedintegeryes–
tablestringyes–

No examples provided.

patrol_snowflake ~941

Check a fact table in Snowflake for data-quality incidents and say which are safe to fix. A patrol checks every daily partition of the fact table for duplicate keys, duplicate rows, missing partitions, rows that point to no reference record, null spikes, and row counts or amounts that do not match the source's control totals. For each problem it proposes a fix, tests that fix on a copy against the control totals, and decides: "auto-fixed" (proven and low risk), "no action needed" (checked, the data is right) or "escalate" (a person must decide). Use this before trusting, querying or building on a date-partitioned Snowflake table, or after a load to confirm the data is still right. Use patrol_dbt instead when the table is built by a dbt model, patrol_duckdb for a DuckDB file and patrol_files for CSV or Parquet exports. Use run_demo to see the output on sample data. Behavior: connects to Snowflake with credentials already configured on this machine; none are passed as arguments. It runs three SELECT statements and nothing else, so the warehouse is never modified, and it selects only the mapped columns for the last `days` days, so it uses a little warehouse compute (usually seconds for 30 days). The only side effect is writing four report files to out_dir: dashboard.html, audit.jsonl, incidents.csv and fixed_version.csv (the proposed corrected table, for review). Fails with a readable error if the login is refused, or a table or mapped column does not exist. Returns the counts (incidents, auto_fixed, no_action_needed, escalate), needs_a_person (the escalated incidents), all_incidents (partition, problems, decision, proposed_fix, residual for each) and outputs (paths to the report files). Pass outputs.folder and a partition to get_incident for the full evidence behind one decision. Tell the user about every escalated incident.

NameTypeReqDescription
amountstring–Numeric amount column in the fact table. It is compared with the 'amount' control total.
category––Optional categorical column in the fact table. Omit if the table has none.
connection––Name of a connection in ~/.snowflake/connections.toml. Omit to use the server's SNOWFLAKE_ACCOUNT, SNOWFLAKE_USER, SNOWFLAKE_PASSWORD or SNOWFLAKE_PRIVATE_KEY_PATH, SNOWFLAKE_ROLE and SNOWFLAKE_WAREH…
datestring–Date column the fact table is partitioned by, one partition per calendar day. The control totals must have a column with the same name.
days––Read only the last N days of the fact table and control totals (today counts as day one). Use at least 30 so the checks have a baseline. Pass null to read the whole table, which can be slow and costl…
keystring–Column in the fact table that uniquely identifies a row (the primary key).
manifest_tablestringyesTable of the source system's control totals, one row per date and segment, with columns: the date column, the segment column ('*' = whole day), n (row count) and amount (sum).
out_dir––Folder to write the report files into. Created if missing; report files already there are overwritten. Omit to use a new temporary folder; its path comes back in outputs.folder.
ref_keystring–Column in the reference table that the fact table's reference column must match.
ref_tablestringyesReference table that fact rows point to, for example ANALYTICS.GOLD.CUSTOMERS.
referencestring–Column in the fact table that points to the reference table (the foreign key).
segmentstring–Column that splits each day into segments, for example channel or region. The control totals must have a column with the same name, where '*' means the whole day.
tablestringyesFact table to check, for example ANALYTICS.GOLD.PAYMENTS. An unqualified name uses the connection's database and schema.
threshold––Gate threshold: the largest relative gap to the control totals that a verified fix may leave and still be marked auto-fixed (0.01 = 1%). Lower is stricter. Omit for the benchmark-calibrated default,…
NameTypeReqDescription
all_incidentsarrayyes–
auto_fixedintegeryes–
escalateintegeryes–
gate_thresholdnumberyes–
incidentsintegeryes–
needs_a_personarrayyes–
no_action_neededintegeryes–
notestringyes–
outputs–yes–
rows_checkedintegeryes–
tablestringyes–

No examples provided.

run_demo ~263

Run a patrol on generated sample data, to see what DataRanger reports without touching real data. Generates 60 days of synthetic payment transactions with planted problems (duplicates, missing days, orphan rows, wrong amounts and some harmless decoys), then patrols them exactly as patrol_duckdb and patrol_files do. Use this to try DataRanger, to show a user the report format, or to test your own handling of the results. Use patrol_duckdb or patrol_files for real tables. Behavior: needs no input data, credentials or network. The only side effect is writing the report files (dashboard.html, audit.jsonl, incidents.csv, fixed_version.csv) to out_dir. Takes a few seconds. Returns the same summary as the patrol tools: counts, needs_a_person, all_incidents and outputs. Pass outputs.folder and a partition to get_incident for the evidence behind one decision.

NameTypeReqDescription
out_dir––Folder to write the report files into. Created if missing; report files already there are overwritten. Omit to use a new temporary folder; its path comes back in outputs.folder.
seedinteger–Random seed for the generated data. The same seed on the same day gives the same table.
NameTypeReqDescription
all_incidentsarrayyes–
auto_fixedintegeryes–
escalateintegeryes–
gate_thresholdnumberyes–
incidentsintegeryes–
needs_a_personarrayyes–
no_action_neededintegeryes–
notestringyes–
outputs–yes–
rows_checkedintegeryes–
tablestringyes–

No examples provided.

Install

How do I install the DataRanger MCP server?

DataRanger runs locally as a PyPI package, launched with uvx dataranger mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · dataranger

# add to Claude Code
claude mcp add akshaysharma1088-dataranger -- uvx dataranger mcp
Common questions

What is the DataRanger MCP server?

DataRanger is an MCP server listed in the public MCP registry as io.github.akshaysharma1088/dataranger. Read-only data patrol for AI agents: find broken partitions, prove fixes, escalate the rest. This page covers its PyPI package (dataranger).

Is the DataRanger MCP server safe to use?

DataRanger scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DataRanger MCP server expose?

DataRanger exposes 6 tools: patrol_duckdb, patrol_files, patrol_snowflake, patrol_dbt, get_incident, run_demo. Their descriptions and schemas cost roughly 4,168 tokens of context every time the server is loaded.

Is the DataRanger MCP server still maintained?

DataRanger is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the DataRanger MCP server under?

DataRanger declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the DataRanger MCP server?

VerifyMCP ran 15 checks on DataRanger, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about DataRanger: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.