Prozorro Sale
NPM · @PIPEWORX/MCP-PROZORRO-SALE · 2 COMPONENTS
Prozorro.Sale MCP — Ukraine's state and municipal asset sales and leases (keyless).
Available components
Last scanned (17 hours ago)
Scores higher than 72% of npm servers
Category E-commerce
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-prozorro-sale). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 960 tokens (~240/item across 4 items; 4 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 Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- 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
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.
- 5 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.
- 4 Nov 26 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-prozorro-sale@0.2.1
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-prozorro-sale |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-prozorro-sale/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691865838 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ec973f2b4734163a65688bbb1ac8dab4c9e06c42b56a9dec41d8df9e1512abdd3d1ccc9c6e06040f35214c0f477224d66029609df98df5be288f5a017 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
prozorro_sale_asset ~100
Look up a Prozorro.Sale registry object — usually a privatisation ASSET (id like "RAS001-UA-20260512-28803") or its 24-hex registry id — with its title, status, holder, items and the auctions it was offered in. Find asset ids in prozorro_sale_procedure related_entities.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Asset id (RAS…) or 24-hex registry id. |
No output schema declared.
No examples provided.
prozorro_sale_changes ~116
Incremental feed of Prozorro.Sale procedures modified on/after a timestamp, oldest first — the upstream change feed. Returns summaries plus next_since to continue from. Use to track new auctions, status changes and results since a point in time.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Records to return, 1-100 (default 25). |
| since | string | yes | ISO date or datetime, e.g. "2026-10-01" or "2026-10-01T12:00:00". |
No output schema declared.
No examples provided.
prozorro_sale_procedure ~167
Full detail of one Prozorro.Sale auction by its public auction id (e.g. "LRE001-UA-20260813-89379") or internal 24-hex id: items (cadastral numbers, areas, addresses), start price, guarantee, bids with amounts and bidder organisations, awards, signed contracts, cancellations, related registry assets, and the REPEAT-AUCTION CHAIN (earlier failed attempts and later repeats of the same lot). Protected-record flags are passed through verbatim.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Public auction id (e.g. LRE001-UA-20260813-89379) or the 24-hex internal id. |
| include_chain | boolean | – | Walk the repeat-auction chain (default true). |
No output schema declared.
No examples provided.
prozorro_sale_search ~521
Search Prozorro.Sale, Ukraine's public auction system for STATE and MUNICIPAL asset sales and leases (not procurement — for tenders use prozorro_search_tenders). Covers land-lease and land-sale auctions, municipal/state property leases, small privatisation, bankruptcy estates, timber, railway cargo, subsoil. Filter by direction (auction family), status, region (oblast), locality, free text, start-price range and modified date. Returns procedures newest-modified first with status, start price, region, seller, bid count and the upstream protected-record flags. Text is Ukrainian as published.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | metaInfo category, e.g. agriLandLease, otherLandLease, agriLandSale, realEstateLease, commercialSale, cars. |
| direction | string | – | Auction family (metaInfo.directions). Known values: landRental (land-lease rights), landSell, landArrested (seized land), legitimatePropertyLease and commercialPropertyLease (state/municipal property… |
| limit | number | – | Results per page, 1-100 (default 20). |
| locality | string | – | Settlement as published, e.g. "м.Бровари". |
| max_value | number | – | Maximum start price (UAH). |
| min_value | number | – | Minimum start price (UAH). |
| modified_since | string | – | Only procedures modified on/after this date (YYYY-MM-DD or ISO datetime). |
| page | number | – | Page number (default 1). |
| query | string | – | Full-text search over titles and descriptions (Ukrainian works best), e.g. "Бровари" or a cadastral number. |
| region | string | – | Oblast as published in Ukrainian, e.g. "Київська область", "Львівська область". English oblast names (e.g. "Kyiv", "Lviv") are translated. |
| selling_method | string | – | Exact sellingMethod, e.g. landRental-english, smallPrivatization-dutch, legitimatePropertyLease-priorityEnglish. |
| status | string | – | Procedure status, e.g. active_tendering (open for bids), active_rectification, active_auction, active_qualification, active_awarded, pending_payment, complete, unsuccessful, cancelled. |
No output schema declared.
No examples provided.
How do I install the Prozorro Sale MCP server?
Prozorro Sale runs locally as an npm package, launched with npx -y @pipeworx/mcp-prozorro-sale. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-prozorro-sale
claude mcp add pipeworx-io-prozorro-sale -- npx -y @pipeworx/mcp-prozorro-sale
What is the Prozorro Sale MCP server?
Prozorro Sale is an MCP server listed in the public MCP registry as io.github.pipeworx-io/prozorro-sale. Prozorro.Sale MCP, Ukraine's state and municipal asset sales and leases (keyless). This page covers its npm package (@pipeworx/mcp-prozorro-sale).
Is the Prozorro Sale MCP server safe to use?
Prozorro Sale scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Prozorro Sale MCP server expose?
Prozorro Sale exposes 4 tools: prozorro_sale_search, prozorro_sale_procedure, prozorro_sale_asset, prozorro_sale_changes. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.
Is the Prozorro Sale MCP server still maintained?
Prozorro Sale is still listed as active in the MCP registry. We last reached this channel on 5 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 Prozorro Sale MCP server under?
Prozorro Sale 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 Prozorro Sale MCP server?
VerifyMCP ran 16 checks on Prozorro Sale, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.