pipeverify
PYPI · PIPEVERIFY
Read-only check that a pipeline change left the data right: pass, review or block.
Available components
Last scanned (10 hours ago)
Scores higher than 61% of PyPI servers
Category Testing and QA
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 30 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/pipeverify). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1956 tokens (~652/item across 3 items; 3 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 Management27
- Stability observed for 8 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 →
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 0
- Package version: 0.3.1 → 0.3.4 functional
- Package version: 0.3.1 → 0.3.3 functional
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.3.0 → 0.3.1 functional
- 13 Nov 26 79
First indexed and scored.
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/pipeverify@0.3.4
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/pipeverify |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/akshaysharma1088/pipeverify/.github/workflows/release.yml@refs/tags/v0.3.4 |
| Rekor log index | 4026890326 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d9ee7f87a05b93a1aa565a7963dd140d9d89cd9a7f5743bfe840200b806621ef |
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 30 packages
| Packages resolved | 30 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_against_source ~707
Check an output table against the raw source it was built from, when there is no "before" to compare. It catches a transformation that looks clean but decided something it had no basis for: the source sent two different amounts for one key and the output kept one without saying so, values that no longer match the source, source rows that never arrived, or output rows with no source at all. Use this for a new table, a first load, or a dedupe or repair step, where compare_tables has nothing to compare with. Use compare_tables when you do have the table from before the change; you can run both for the strongest check. Behavior: read-only and repeatable. The table and the source are each read once (files are opened read-only; Snowflake, dbt and SQL sources run one SELECT each, with credentials already configured on this machine) and loaded into a temporary in-memory DuckDB. Nothing is written anywhere. Usually takes seconds. Fails with a readable error if a file, table, key or column does not exist. Returns verdict ("pass", "review" or "block"), headline (one sentence you can show the user), and tables: one entry with stats and findings, each with check, severity, message, column and metrics. A "review" here usually means the source itself is ambiguous, so a person must choose; say so.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | – | – | Which checks to run, from: conflict (the source has conflicting values for a key and the output silently kept one), mismatch (an output value differs from its source value), missing (a source key is… |
| columns | – | – | Columns to compare, as {output column: source column}, for example {"amount": "amt"}. Needed for the conflict and mismatch checks; omit to check only keys. |
| key | array | yes | Column or columns that identify one row in the output, for example ["txn_id"]. |
| name | – | – | Name to show for the table in the report. Defaults to 'table'. |
| source | – | yes | The raw input the output was built from (for example the bronze table or landing file). Same forms as 'table'. |
| source_key | – | – | The key column or columns in the source, in the same order as 'key', when they are named differently. Omit if the names match. |
| table | – | yes | The output table to check (for example a silver or gold table). A file path (.csv, .parquet, .json, .xlsx; CSV and JSON may be .gz or .zst), 'duckdb:<file.db>:<table or SELECT>', 'snowflake:<DB.SCHEM… |
| where | – | – | SQL filter for the source rows that should reach the output, for example "status <> 'test'". Omit when every source row should. |
| Name | Type | Req | Description |
|---|---|---|---|
| headline | string | yes | – |
| seconds | number | yes | – |
| tables | array | yes | – |
| verdict | string | yes | – |
| version | string | yes | – |
No examples provided.
compare_tables ~790
Compare one table before and after a pipeline change and say whether the change harmed the data. It looks for the damage that a green job and passing tests miss: rows lost or duplicated (a join that fans out, a dedupe that drops too much), keys that disappeared, values that changed in columns the change was not meant to touch, a jump in nulls, a shifted total (a unit or currency change), new or vanished categories, and schema or type changes. Use this after you edit a SQL query, dbt model, Spark job or load, or after an agent applies a fix, and before you report the work as done, merge it or publish the table. Use check_against_source instead when there is no earlier snapshot but you have the raw input the table was built from, and run_config when the project already has a pipeverify.yml listing its tables. Behavior: read-only and repeatable. Both snapshots are read (files are opened read-only; Snowflake, dbt and SQL sources run one SELECT each, with credentials already configured on this machine, never passed as arguments) and loaded into a temporary in-memory DuckDB where the checks run. Nothing is written anywhere. Each snapshot is loaded whole, so for a large warehouse table pass a SELECT or a 'where' filter covering the slice you changed. Usually takes seconds. Fails with a readable error if a file, table, dbt model, key column or login is wrong. Returns verdict ("pass", "review" or "block"), headline (one sentence you can show the user), and tables: one entry with stats (row counts and more) and findings, each with check, severity, message, column and metrics. On "review" or "block", tell the user every finding and do not apply the change.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | yes | The same table after the change (for example the pull request's build). Same forms as 'before'. |
| before | – | yes | The table as it was before the change (for example production, or yesterday's snapshot). A file path (.csv, .parquet, .json, .xlsx; CSV and JSON may be .gz or .zst), 'duckdb:<file.db>:<table or SELEC… |
| expect_change | – | – | Columns this change is meant to modify. Differences in them are reported as expected instead of flagged. Omit when the change should not alter any existing value. |
| expect_row_change | boolean | – | Set true when the change is meant to add or remove rows, so a row-count change alone is not flagged. |
| ignore | – | – | Columns to skip because they always differ, such as load timestamps or run ids. |
| key | – | – | Column or columns that together identify one row, for example ["order_id"] or ["store_id", "sale_date"]. Without a key only table-level checks run (row counts, schema, null rates, totals), so give on… |
| name | – | – | Name to show for the table in the report, for example gold.daily_sales. Defaults to 'table'. |
| thresholds | – | – | Optional overrides for when a difference becomes review or block, in percent of rows, for example {"row_change_block_pct": 20, "sum_shift_review_pct": 1}. Omit to use the defaults. |
| Name | Type | Req | Description |
|---|---|---|---|
| headline | string | yes | – |
| seconds | number | yes | – |
| tables | array | yes | – |
| verdict | string | yes | – |
| version | string | yes | – |
No examples provided.
run_config ~311
Check every table listed in a project's pipeverify.yml and return one overall verdict. Use this when the project already has a pipeverify config, which is the same check its CI runs, so you see what the pull request check will say before you push. Use compare_tables for a one-off comparison of two snapshots without a config file. Behavior: read-only and repeatable. Reads the config, then reads each table's snapshots (files, DuckDB, Snowflake, dbt models or SQL databases, using credentials already configured on this machine) into a temporary in-memory DuckDB. Nothing is written anywhere. Time grows with the number and size of the tables. A table that cannot be read is reported as "block" with the reason in its error field, and the remaining tables are still checked. Fails with a readable error if the config file is missing, is not valid, or no table matches. Returns verdict (the worst across tables: "pass", "review" or "block"), headline, and tables: one entry per table with its own verdict, stats, error and findings. Tell the user every review and block finding.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | – | Path to a pipeverify config file, usually pipeverify.yml in the project root. It lists each table with its before, after, key and options. |
| tables | – | – | Only check the tables with these names (the 'name' entries in the config). Omit to check every table. |
| Name | Type | Req | Description |
|---|---|---|---|
| headline | string | yes | – |
| seconds | number | yes | – |
| tables | array | yes | – |
| verdict | string | yes | – |
| version | string | yes | – |
No examples provided.
How do I install the pipeverify MCP server?
pipeverify runs locally as a PyPI package, launched with uvx pipeverify 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 · pipeverify
claude mcp add akshaysharma1088-pipeverify -- uvx pipeverify mcp
What is the pipeverify MCP server?
pipeverify is an MCP server listed in the public MCP registry as io.github.akshaysharma1088/pipeverify. Read-only check that a pipeline change left the data right: pass, review or block. This page covers its PyPI package (pipeverify).
Is the pipeverify MCP server safe to use?
pipeverify 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 pipeverify MCP server expose?
pipeverify exposes 3 tools: compare_tables, check_against_source, run_config. Their descriptions and schemas cost roughly 1,808 tokens of context every time the server is loaded.
Is the pipeverify MCP server still maintained?
pipeverify 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 pipeverify MCP server under?
pipeverify declares the Apache-2.0 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 pipeverify MCP server?
VerifyMCP ran 15 checks on pipeverify, 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 pipeverify: 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.