# Prozorro (npm · @pipeworx/mcp-prozorro)

ProZorro MCP — Ukraine government procurement (keyless).

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-prozorro/prozorro-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-prozorro/prozorro-mcp)
- npm · `@pipeworx/mcp-prozorro`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-prozorro/pipeworx-mcp-prozorro.md), [page](https://verifymcp.io/servers/pipeworx-io-prozorro/pipeworx-mcp-prozorro)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-prozorro`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-prozorro).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2409 tokens (~401/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Prozorro MCP server?

Prozorro runs locally as an npm package, launched with npx -y @pipeworx/mcp-prozorro. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-prozorro -- npx -y @pipeworx/mcp-prozorro
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-prozorro": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-prozorro"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-prozorro": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-prozorro"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-prozorro -- npx -y @pipeworx/mcp-prozorro
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-prozorro": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-prozorro"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-prozorro --command npx --arg -y --arg @pipeworx/mcp-prozorro
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-prozorro:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-prozorro"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-prozorro": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-prozorro"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-prozorro -t stdio -c npx -a -y @pipeworx/mcp-prozorro
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-prozorro": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-prozorro"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +3)

- [security regression] 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.
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (6)

### `prozorro_recent_tenders` (~123 tokens)

Most recently updated tenders from Ukraine's ProZorro national procurement system (via the keyless OpenProcurement public feed). Returns each tender with id, tenderID, title, value (amount+currency, usually UAH), buyer (procuring entity), status, and procurement method. Titles and buyer names are in Ukrainian. Use for browsing current Ukrainian public tenders; for a specific tender use prozorro_get_tender.

Input parameters:

- `limit` (number|string): How many recent tenders to return (1-50). Default 20.

### `prozorro_search_tenders` (~743 tokens)

Full-text search over ALL Ukraine ProZorro tenders back to 2015 (keyless). Searches ProZorro's own analyzed index, so Ukrainian queries stem correctly ("школа" also matches "школи", "шкільний") — pass Ukrainian keywords for best recall. Filter by buyer EDRPOU, by SUPPLIER/bidder EDRPOU (`tenderer` — this is the one for supplier due diligence: every tender a company has bid on or won), CPV code, status, value range, and date. date_from/date_to ALONE (no query/tenderer/buyer/cpv) is also valid and is the only live way to BROWSE historical ProZorro tenders by date — e.g. "what did ProZorro buy in March 2015" — verified live: a bare 10-day 2015 window returns a correctly-dated, narrow result set, not the unfiltered corpus. Returns tenderID, title, value, buyer name + EDRPOU + region, status, and an `id` field (internal 32-hex id) that is NULL unless `resolve_ids` is passed — the search index itself never carries it (verified live); prozorro_get_tender with just the tenderID now attempts the same resolution automatically, so you usually don't need `resolve_ids` here. For an OLD tenderID found this way whose full award/contract detail prozorro_get_tender can't resolve (outside the recently-modified window), use prozorro_historical_release instead.

Input parameters:

- `buyer` (string): Buyer/procuring-entity EDRPOU code (8 digits).
- `cpv` (string): Exact CPV classification code, e.g. "09111100-1".
- `date_from` (string): Start date YYYY-MM-DD. Valid ALONE (no other filter) to browse a historical window — e.g. date_from:"2015-03-01", date_to:"2015-03-10". Combined with a keyword/tenderer/buyer query, note it filters o…
- `date_to` (string): End date YYYY-MM-DD. Same rules as date_from.
- `order` (string): "desc" (default) or "asc".
- `page` (number|string): Page number, 1-500. Fixed 20 results per page.
- `query` (string): Free-text query, Ukrainian recommended (e.g. "вугілля", "школа"). Optional if you pass a filter such as tenderer, buyer, or a date range.
- `resolve_ids` (boolean): Best-effort: try to fill in each result's `id` (the internal 32-hex id prozorro_get_tender needs for full detail) by scanning the most-recently-modified few thousand ProZorro records. Only finds tend…
- `sort_by` (string): "dateCreated" (default) or "value.amount".
- `status` (string): Tender status: complete, active.tendering, cancelled, unsuccessful, …
- `tenderer` (string): Supplier/bidder EDRPOU code (8 digits, e.g. "00131305") — returns every tender this company bid on or won. The primary supplier due-diligence filter.

### `prozorro_search_organizations` (~146 tokens)

Resolve a Ukrainian company or public buyer NAME to its EDRPOU code, using ProZorro's organization index (keyless). This is the entry point for supplier due diligence: a user knows the company's name, but prozorro_search_tenders filters by EDRPOU — call this first, then pass the returned `edrpou` as `tenderer` (supplier side) or `buyer` to get that company's full tender history.

Input parameters:

- `name` (string, required): Company or buyer name, Ukrainian recommended.
- `role` (string): "tenderer" for suppliers/bidders (default), or "buyer" for procuring entities.

### `prozorro_get_tender` (~595 tokens)

Full detail for a single Ukraine ProZorro tender by id (via the keyless OpenProcurement public API). Returns tenderID, title, description, status, procurementMethod + procurementMethodType (raw OCDS fields — broad method vs ProZorro's specific type, e.g. aboveThresholdUA/aboveThresholdEU), tender_value (the ORIGINAL ASKING PRICE — not money spent), the buyer/procuring entity (name, EDR identifier, region, contact), tender period (start/end), enquiry period, number of bids, line items (description, CPV classification, quantity, unit, relatedLot), `lots` (id/title/status/value, when the tender is lotted), and the OCDS award/contract stage: `award` (operative award: status, date, value, winning supplier, lotID, bid_id — null if none) plus the full `awards` history (each with the FULL `suppliers[]` array — name + identifier scheme/id — alongside the single-supplier `supplier` field kept for backward compatibility), and `contract` (signed contract value/date, with its CURRENT status and amountPaid read from the contract record — the tender's own copy goes stale after signing; use prozorro_get_contract for amendments, termination and contract documents). An `interpretation` line states plainly whether the tender_value was ever actually spent. Pass `raw:true` to also get the complete, unshaped upstream OCDS tender object under `raw`, for any field not shaped above. Text is largely Ukrainian. Accepts the internal 32-char tender id OR a human tenderID ("UA-2026-09-20-000012-a") — for a tenderID this now tries to resolve the internal id by scanning the most-recently-modified feed records first (cheap, usually one call for anything modified in the last few hours) and returns FULL detail when that succeeds; it falls back to the search index's summary (detail_available:false, no awards) only when the tender wasn't modified recently enough to be found that way.

Input parameters:

- `id` (string, required): Tender id — the internal 32-hex id (e.g. "156db6e773ba4b6e925d00f9ad3b13f4") from prozorro_recent_tenders always returns full detail. A human tenderID ("UA-2026-09-20-000012-a") from prozorro_search_…
- `raw` (boolean): Include the complete, unshaped upstream OCDS tender JSON under `raw`. Only applies when full detail is available (detail_available:true). Default false — the raw object can be large (documents, full…

### `prozorro_get_contract` (~417 tokens)

The authoritative post-award contract record(s) for a Ukraine ProZorro tender (keyless OpenProcurement contracting API): current status (active | terminated | cancelled), dateSigned, contract period, current value (AFTER amendments — the API does not keep the original signed amount as a separate field; the change rationale usually states it) and amountPaid, terminationDetails, every contract change/amendment (rationale, rationaleTypes, date published, dateSigned), contract documents with their datePublished, and milestones. Use this — not the tender — for anything after signing: the copy of the contract embedded in a tender is frozen when the tender completes and keeps saying `active` after the contract is amended or terminated. Pass a tender id (32-hex or UA-… tenderID) to get all of its contracts, or a contract's 32-hex id. Optional `as_of` (YYYY-MM-DD) splits changes and documents into those published on/before vs after that date and states whether the record's status at that date is known: the public API keeps NO revision history, so if the record was modified after `as_of` the status at `as_of` is reported as not available rather than inferred. The API carries no termination date field; this tool never invents one.

Input parameters:

- `as_of` (string): Optional cutoff date YYYY-MM-DD (or full ISO timestamp). Separates what was published on or before it from what came later, and says whether the status at that date can be established from the public…
- `id` (string, required): A tender id (internal 32-hex, e.g. "6a9dca3807a14b37bf82fb8ad2eae0c9", or human tenderID "UA-2026-07-13-009811-a") to return every contract of that tender, or a contract's own 32-hex id (the `contrac…

### `prozorro_historical_release` (~331 tokens)

Detail for a Ukraine ProZorro tender that prozorro_get_tender can't resolve from a human tenderID — its tenderID-to-internal-id lookup only scans the most-recently-modified few thousand records (fleet #2762/#2768), so a tenderID found via prozorro_search_tenders' date-range browsing (e.g. a 2015 tender) comes back `detail_available:false` there. An internal 32-hex id ALWAYS resolves immediately regardless of age (a direct lookup, no scan needed). For a human tenderID this tries TWO live strategies before giving up: the same recently-modified scan prozorro_get_tender uses, then a bounded forward scan seeded from the DATE THE TENDERID ITSELF ENCODES ("UA-2015-02-16-..." -> search from 2015-02-16) — this finds it when the tender's last modification happened reasonably soon after that date, and does not when a later amendment moved it far down the feed; both are live, keyless, no stored data (fleet #3244). `source` says which path answered; `detail_available:false` (never a crash, never an empty object) means neither reached it, and only the search-index summary is available.

Input parameters:

- `id` (string, required): Tender id — internal 32-hex (e.g. "09076ffc415e4d57ad7046aacc91b6e1") or human tenderID (e.g. "UA-2015-02-16-000001").

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-prozorro/pipeworx-mcp-prozorro#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Prozorro MCP server?

Prozorro is an MCP server listed in the public MCP registry as io.github.pipeworx-io/prozorro. ProZorro MCP, Ukraine government procurement (keyless). This page covers its npm package (@pipeworx/mcp-prozorro).

### Is the Prozorro MCP server safe to use?

Prozorro scores 81 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 MCP server expose?

Prozorro exposes 6 tools: prozorro_recent_tenders, prozorro_search_tenders, prozorro_search_organizations, prozorro_get_tender, prozorro_get_contract, prozorro_historical_release. Their descriptions and schemas cost roughly 2,355 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 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 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.

### What did VerifyMCP test on the Prozorro MCP server?

VerifyMCP ran 16 checks on Prozorro, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-prozorro
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-prozorro
- Repository: https://github.com/pipeworx-io/mcp-prozorro
- Website: https://pipeworx.io/packs/prozorro
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-prozorro/pipeworx-mcp-prozorro.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-prozorro/pipeworx-mcp-prozorro/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-prozorro/pipeworx-mcp-prozorro.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-prozorro/pipeworx-mcp-prozorro