Prozorro
PYPI · PROZORRO-MCP
Ukrainian public procurement (Prozorro): open tenders, plans, competitors, red flags. No keys.
Available components
Last scanned (22 hours ago)
Scores higher than 68% of PyPI servers
Category Finance and Payments
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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1302 tokens (~93/item across 14 items; 14 tools + 0 resources), lean.Pass
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 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
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.
- 22 Oct 26 +18
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.27 ▲ functional
- 20 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Oct 26 +27
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 13 Oct 26 39
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 22 Oct 2026 · Analysed pypi/prozorro-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
buyer_profile ~50
Buyer profile by EDRPOU: what it buys, from whom, procedure mix, share of competitive tenders with a single bidder.
| Name | Type | Req | Description |
|---|---|---|---|
| edrpou | string | yes | – |
| since | – | – | – |
No output schema declared.
No examples provided.
competitors ~61
Who competes with a company (EDRPOU): bidders met most often in the same tenders, and how many of those tenders each side won.
| Name | Type | Req | Description |
|---|---|---|---|
| edrpou | string | yes | – |
| since | – | – | – |
| top | integer | – | – |
No output schema declared.
No examples provided.
coverage ~45
What the local data covers: regions, period, CPV filter, counts, last sync, the background sync progress if any, and how to add more. Call this first when unsure.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_entity ~56
Find buyers and suppliers by part of a name (or an exact EDRPOU code). role: any, buyer, supplier.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | yes | – |
| role | string | – | – |
No output schema declared.
No examples provided.
get_tender ~49
One tender in full by its UA-... id: items with quantities and CPV, lots, every bid, the winner, and documents with direct links.
| Name | Type | Req | Description |
|---|---|---|---|
| tender_id | string | yes | – |
No output schema declared.
No examples provided.
market_overview ~84
Market for a CPV and/or region over a period: number and value of tenders, awarded sum, share of competitive procedures, average bidders, unit-price spread (P25/median/P75, same CPV and unit), top buyers and winners.
| Name | Type | Req | Description |
|---|---|---|---|
| cpv | – | – | – |
| region | – | – | – |
| since | – | – | – |
| top | integer | – | – |
No output schema declared.
No examples provided.
red_flags ~143
Red flags for a buyer (EDRPOU), CPV or region, each with evidence and a link: single_bidder, supplier_concentration (one supplier > share of a buyer's spend), price_above_median (unit price pct above peers), short_tender_period. A flag is a reason to look closer, not proof.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | – | – | – |
| cpv | – | – | – |
| kinds | – | – | – |
| limit | integer | – | – |
| min_awards | integer | – | – |
| min_peers | integer | – | – |
| pct | number | – | – |
| region | – | – | – |
| share | number | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
search_tenders ~141
Search tenders. Words match the title and item descriptions; cpv is a ДК 021 code, prefix or words; region in any spelling; status: open (default, accepting bids), any, or a Prozorro status. Dates as 2026-10-01, 7d or 24h. Returns tender ids, buyers, amounts, deadlines and links.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_max | – | – | – |
| amount_min | – | – | – |
| cpv | – | – | – |
| deadline_after | – | – | – |
| limit | integer | – | – |
| published_since | – | – | – |
| query | – | – | – |
| region | – | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
supplier_profile ~65
Supplier profile by EDRPOU: wins and their value, main buyers and CPVs, win rate where it bid, median discount from the expected value. Use find_entity to get the code from a name.
| Name | Type | Req | Description |
|---|---|---|---|
| edrpou | string | yes | – |
| since | – | – | – |
No output schema declared.
No examples provided.
sync_data ~149
Download Prozorro tenders and plans for regions (any spelling) into the local data, in the background. Call it only after the user agreed to the download. days: how far back; the user chooses it for the first download, later downloads keep the synced period unless the user asks for another. cpv: categories to download, added to those already synced (nothing changes when all categories are synced). Without arguments it fetches what changed since the last sync. Regions are added to what is already synced; a new region, category or period walks the whole period again. Returns at once; check coverage for progress.
| Name | Type | Req | Description |
|---|---|---|---|
| cpv | – | – | – |
| days | – | – | – |
| regions | – | – | – |
No output schema declared.
No examples provided.
upcoming_plans ~83
Upcoming purchases from annual plans that have no tender yet: see demand before it is announced. Filter by words, CPV, region, budget, planned start date.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_max | – | – | – |
| budget_min | – | – | – |
| cpv | – | – | – |
| limit | integer | – | – |
| query | – | – | – |
| region | – | – | – |
| start_from | – | – | – |
No output schema declared.
No examples provided.
watch_add ~70
Save a search under a name (words, CPV code or words, region in any spelling) so watch_digest shows its new tenders. Call it when the user asks to follow something.
| Name | Type | Req | Description |
|---|---|---|---|
| cpv | – | – | – |
| name | string | yes | – |
| query | – | – | – |
| region | – | – | – |
No output schema declared.
No examples provided.
watch_digest ~58
New tenders for the user's saved searches since a moment (default: last 24 hours). Saved searches are added with watch_add or the CLI: prozorro-mcp watch add.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
watch_remove ~33
Delete a saved search by its name. Only when the user asks to stop following it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Prozorro MCP server?
Prozorro runs locally as a PyPI package, launched with uvx prozorro-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 · prozorro-mcp
claude mcp add kotiniiqq-prozorro-mcp -- uvx prozorro-mcp
What is the Prozorro MCP server?
Prozorro is an MCP server listed in the public MCP registry as io.github.kotiniiqq/prozorro-mcp. Ukrainian public procurement (Prozorro): open tenders, plans, competitors, red flags. No keys. This page covers its PyPI package (prozorro-mcp).
Is the Prozorro MCP server safe to use?
Prozorro scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. 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 MCP server expose?
Prozorro exposes 14 tools: coverage, sync_data, find_entity, search_tenders, get_tender, and 9 more. Their descriptions and schemas cost roughly 1,087 tokens of context every time the server is loaded.
Is the Prozorro MCP server still maintained?
Prozorro is still listed as active in the MCP registry. We last reached this channel on 22 October 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 MCP server under?
Prozorro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.