Prozorro Sale

io.github.pipeworx-iov0.1.0Updated Oct 10, 2026

Prozorro.Sale MCP — Ukraine's state and municipal asset sales and leases (keyless).

VerifiedStreamable HTTPWeb executableBusiness & CommerceFinance

Overview

AI-generated overview

Lets an assistant search and inspect Ukraine's Prozorro.Sale public auctions of state and municipal assets, bids, awards and contracts.

What it does
Provides keyless access to the public Prozorro.Sale auction system covering land lease and sale, property leases, small privatisation, bankruptcy estates, timber, railway cargo and subsoil rights. Tools search auctions by direction, status, region, locality, selling method, category, value range and modification date, fetch a single procedure with items, bids, awards, contracts and repeat-auction chain, look up a registry asset, and stream the upstream modified-date feed. Responses carry a data-as-of marker; unknown ids return found: false.
When to use it
Use it when you need current or historical information about Ukrainian state and municipal asset auctions, such as finding land-lease auctions open for bids in a given oblast, checking who won a lot, or tracking changes to procedures over time.
Requirements
A remote streamable HTTP endpoint at the gateway URL, or a local stdio server started with npx. No account, API key or environment variable is declared for the pack's own tools; network access to the gateway and the upstream public API is needed.
Before you install
The gateway connection also exposes shared Pipeworx meta-tools, including ask_pipeworx routing and remember/recall, so the listed tool count is larger than this pack's own tools and the connection's initialize response is authoritative. The integration is independent and unofficial. Upstream masks bidder addresses and contacts, and the pack additionally drops contact-person names and individual tax numbers.

Installation

In SourceWeft

  1. Open Prozorro Sale in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "prozorro-sale": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/prozorro-sale/mcp"
    }
  }
}

README

@pipeworx/prozorro-sale

Prozorro.Sale, Ukraine's public auction system for state and municipal asset sales and leases: land-lease and land-sale auctions, municipal and state property leases, small privatisation, bankruptcy estates, timber, railway cargo and subsoil rights, with bids, awards, contracts and the repeat-auction chain.

Part of Pipeworx — an MCP gateway connecting AI agents to 1764+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

  • prozorro_sale_search(direction?, status?, region?, locality?, query?, selling_method?, category?, min_value?, max_value?, modified_since?, limit?, page?) — find auctions, e.g. land-lease auctions open for bids in Kyiv oblast. Newest-modified first, with status, start price, region, seller and bid count.
  • prozorro_sale_procedure(id, include_chain?) — one auction by public id (LRE001-UA-20260813-89379) or internal id: items with cadastral numbers and areas, bids with amounts, awards, signed contracts, cancellations, related registry assets, and the earlier/later repeats of the same lot.
  • prozorro_sale_asset(id) — a registry asset (RAS001-UA-…) with its holder, status and the auctions it was offered in.
  • prozorro_sale_changes(since, limit?) — the upstream modified-date feed, oldest first, with next_since to continue.

Every response carries data_as_of. An unknown id returns found: false; an upstream failure throws with the upstream status.

Auth

Keyless.

Data sources

Notes for the next person:

  • POST /api/search/procedures accepts only {limit, page, sort, filters}; each filter is {field, operator, value}. A wrong field returns a 422 that lists every allowed field — read it rather than guessing.
  • metaInfo.directions is not the sellingMethod prefix: small privatisation is sellOut, basicSell is otherAssets. Filtering on the prefix returns zero rows, not an error.
  • Region filters need the Ukrainian oblast name exactly as published (Київська область); the pack translates common English names.
  • GET /api/search/procedures (no body) answers 204, which looks like an empty result; it is the wrong method.
  • _protected / _protect_level are passed through verbatim. Upstream masks bidder addresses and contacts; the pack also drops contact-person names and individual tax numbers (UA-IPN).

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "prozorro-sale": {      "url": "https://gateway.pipeworx.io/prozorro-sale/mcp"    }  }}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/prozorro-sale/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

json
{  "mcpServers": {    "pipeworx": {      "url": "https://gateway.pipeworx.io/mcp"    }  }}

Both URLs reach the same gateway and the same 1764+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

bash
curl -X POST https://gateway.pipeworx.io/v1/tools/prozorro_sale_search \  -H 'Content-Type: application/json' \  -d '{"direction":"landRental","region":"Київська область","status":"active_tendering","limit":5}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/prozorro_sale_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

bash
npx -y @pipeworx/mcp-prozorro-sale

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Prozorro Sale data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Source: README.md at commit f284389

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 10, 2026