Prozorro.Sale MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Prozorro.Sale MCP Server What land is up for rent near Lviv under 50 000 ₴?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Prozorro.Sale MCP Server
Read-only MCP server for Prozorro.Sale, the Ukrainian state platform that auctions public assets — small and large privatisation, land sale and rental, property lease, timber, subsoil, arrested and bankruptcy assets, sanctioned assets and non-performing loans.
The tools are organised around what people actually ask, not around HTTP endpoints. There is
no GET /procedures/{id}/documents/{doc_id}/history tool; there is "show me the documents for
this auction". Nothing writes: no bids are placed, no procedures are created or modified.
Tools
Tool | Question it answers |
| "What land is up for rent near Lviv under 50 000 ₴?" |
| "Tell me everything about SPD001-UA-20260806-70620." |
| "How long do I have left to bid, and what happens next?" |
| "What did it finally sell for, and how many bidders were there?" |
| "Give me the technical specification and the signed contract." |
| "Is this starting price reasonable for this kind of asset?" |
| "What new lots appeared in my niche since yesterday?" |
| "How much timber was auctioned last week, and how much of it sold?" |
| "Which asset programmes and auction formats exist?" |
| "If I list a lot today, how soon can the auction run?" |
Every tool accepts the public auction id printed on the website
(LRE001-UA-20260708-03894) as well as the internal 24-character procedure id.
Related MCP server: cannons-auctions-mcp
Tool reference
search_auctions
Entry point for any "what is available" question.
Parameter | Type | Notes |
|
| Asset programme or exact selling method. |
|
| "What can I bid on" — keeps only auctions whose deadline has not passed. |
|
| Ukrainian free text over title, description, items, classification and locality. All words must match. |
|
| e.g. |
|
| Substring of oblast or settlement, e.g. |
|
| CAV/CPV code or prefix, e.g. |
|
| Starting-price band. |
|
| The body running the auction — on state-property leases usually a regional SPFU office, not the institution. |
|
| The organisation the asset belongs to (балансоутримувач). See Owner vs seller. |
|
| ISO date bounds on publication. |
|
| Scan a specific historical period instead of recent activity. |
|
| Results returned, 1–100. Default 20. |
|
| Feed pages to scan, 1–40. Default 8. Raise when results come back thin or truncated. |
// Property lease near Lviv, still open, under 50 000 UAH
{"procedure_type": ["legitimatePropertyLease"], "open_for_bids": true,
"region": "Львів", "max_value": 50000, "limit": 10}
// Everything privatisation-related that concluded in July 2026
{"procedure_type": ["smallPrivatization", "largePrivatization"], "status": ["complete"],
"changed_since": "2026-07-01", "changed_until": "2026-07-31", "scan_pages": 25}Returns compact summaries plus a scanned block. An empty result means "not in the scanned
window", never "does not exist".
Owner vs seller
On the legitimatePropertyLease family the two roles are different organisations. A room in a
university building is auctioned by the regional SPFU office, so the university appears as
propertyOwner (балансоутримувач) and never as seller. Filtering by seller for an institution
returns nothing at all.
// Everything Lviv Polytechnic put up for lease this year — EDRPOU is exact, prefer it to a name
{"procedure_type": ["legitimatePropertyLease"], "property_owner_edrpou": "02071010",
"changed_since": "2026-01-01", "changed_until": "2026-08-06", "scan_pages": 40}Only that family publishes the distinction; for every other programme relatedOrganizations is
absent, the seller owns what it sells, and property_owner matches nothing. There is no silent
fallback to text search — combine with keyword if you need one.
get_auction
Everything about one auction. For deadlines alone use get_auction_timeline; for the outcome
alone use get_auction_results — both return far less.
Parameter | Type | Notes |
|
| Public auction id or 24-character procedure id. |
|
| Sections to expand. Default |
include values: items (area, cadastral number, address, classification) · terms
(starting price, minimal step, guarantee deposit, registration fee, lease duration, conditions,
restrictions) · documents · questions · bids · awards · contracts.
// Full picture before deciding whether to bid
{"auction": "SPD001-UA-20260806-70620",
"include": ["items", "terms", "documents", "questions"]}
// Minimal lookup
{"auction": "LRE001-UA-20260708-03894"}get_auction_timeline
The stage clock: what has passed, what is running, what is next, how long is left to bid.
Parameter | Type | Notes |
|
| Public auction id or procedure id. |
|
| Also list archived revisions, showing when the seller amended the terms. Default |
{"auction": "LRE001-UA-20260708-03894"}
{"auction": "LRE001-UA-20260708-03894", "include_revisions": true}Returns the status with its plain-language meaning, every stage marked
past/current/upcoming, the next deadline, and bidding.closesAt / stillOpen /
hoursRemaining.
get_auction_results
How an auction ended. Works on in-progress auctions too — reports outcome: "in_progress".
Parameter | Type | Notes |
|
| Public auction id or procedure id. No other parameters. |
{"auction": "SPE001-UA-20260729-69703"}Returns outcome (contract_signed · winner_determined · ended_without_winner ·
cancelled_by_seller · in_progress), starting vs final price with priceUpliftPercent, bid
counts, attemptNumber (>1 means the lot failed to sell before), awards, contracts and
cancellation reasons.
get_auction_documents
Published files with direct public download URLs.
Parameter | Type | Notes |
|
| Public auction id or procedure id. |
|
| Case-insensitive substring: |
|
|
|
|
| Also list earlier revisions of replaced files. Default |
// Just the technical specification
{"auction": "SPD001-UA-20260806-70620", "document_type": "technicalSpecifications"}
// The complete paper trail including the signed contract
{"auction": "SPD001-UA-20260806-70620",
"include_attachments_of": ["auction", "awards", "contracts"]}Documents attached to bids are never published.
find_comparable_auctions
Valuation and risk: what similar lots go for and how often they sell.
Parameter | Type | Notes |
|
| The reference auction. |
|
| What a comparable must share. Default |
|
| Default |
|
| 1–50. Default 15. |
|
| Widen the sample when |
// Price benchmark for a land lease (default matching)
{"auction": "LRE001-UA-20260708-03894",
"match_on": ["sellingMethod", "classification"]}
// What similar assets are on the market right now
{"auction": "SPD001-UA-20260806-70620", "concluded_only": false, "limit": 25}Re-listings of the same lot are excluded, so one asset is not counted twice.
track_auction_changes
Cursor-based monitoring. Repeated calls make forward progress without re-reading the same activity.
Parameter | Type | Notes |
|
| ISO instant to watch from. Default 24 hours ago. On follow-up polls pass back the previous response's |
|
| Optional upper bound. |
| Narrow the watch to one niche. | |
|
| 1–100. Default 30. |
|
| Raise when a busy window truncates. |
// First poll of a niche
{"procedure_type": ["landRental"], "region": "Полтав", "limit": 20}
// Follow-up poll using the cursor from the previous response
{"procedure_type": ["landRental"], "region": "Полтав",
"since": "2026-08-06T06:27:21.880000Z"}Each change carries an isNew flag distinguishing brand-new listings from updates. The cursor
is inclusive, so the last auction may repeat once.
analyze_auction_market
Volume and trend questions rather than individual lots.
Parameter | Type | Notes |
|
|
|
|
| Period to analyse. Omit both for the most recent activity. |
| Narrow the population before aggregating. | |
|
| Default 15. Raise for a larger sample. |
// Which regions had the most land activity recently
{"procedure_type": ["landRental", "landSell"], "group_by": "region", "scan_pages": 25}
// How privatisation performed in July 2026
{"procedure_type": ["smallPrivatization"], "since": "2026-07-01", "until": "2026-07-31",
"group_by": "sellingMethod", "scan_pages": 30}Returns count/total/mean/median/min/max starting prices, a status histogram and
soldSharePercentOfSettled — where settled means complete, unsuccessful or cancelled
only, so in-flight procedures do not inflate it. These figures describe the scanned window, not
the whole catalogue.
list_procedure_types
The vocabulary the other tools filter on. Cached; no network cost after the first call. Call
this rather than guessing a procedure_type — an unrecognised value silently returns nothing.
Parameter | Type | Notes |
|
| Substring, e.g. |
|
| Default |
{"filter": "land"}
{}Returns 33 programme families with their auction formats, the exact sellingMethod values, and
the three-letter auction-id prefix each produces (LRE = landRental-english, SPE =
smallPrivatization-english…), plus what each of the ten statuses means.
get_publication_constraints
The only forward-looking tool: if a lot is published today, how soon may the auction run.
Parameter | Type | Notes |
|
| A selling method such as |
{"procedure_type": "landRental-english"}
{"procedure_type": "smallPrivatization"}Returns earliestAuctionStart and noticeDays. Computed live, so it is not cached.
Install
git clone https://github.com/VladyslavMykhailyshyn/prozorro-sale-mcp-server.git
cd prozorro-sale-mcp-server
npm install
npm run buildClaude Code
claude mcp add prozorro-sale -- node /absolute/path/to/prozorro-sale-mcp-server/build/index.jsClaude Desktop / any MCP client
{
"mcpServers": {
"prozorro-sale": {
"command": "node",
"args": ["/absolute/path/to/prozorro-sale-mcp-server/build/index.js"]
}
}
}No API key is needed — Prozorro.Sale publishes this data openly.
Configuration
All optional; see .env.example. The variables are read from the process environment, so set
them in your MCP client's env block.
Variable | Default | Purpose |
|
|
|
| — | Full base URL override |
|
| Per-request timeout |
|
| Feed-page cache lifetime |
|
| Feed pages a search scans by default (100 auctions each) |
|
| Hard ceiling per call |
|
| Retries on network/5xx errors |
The one limitation worth understanding
Prozorro.Sale publishes no full-catalogue search API. The open-data surface is a change feed ordered by modification time, plus a per-selling-method feed of the 100 most recent auctions. There is no "all currently open auctions" endpoint to call.
This server therefore searches by scanning, and it is explicit about what it scanned. Every
discovery tool returns a scanned block:
{
"scanned": {
"coveredFrom": "2026-08-06T06:12:41.000Z",
"coveredTo": "now",
"recordsScanned": 614,
"truncated": true,
"note": "Every auction changed in the last 3h was examined (614 records over 3 segments), then the page budget ran out while reaching further back. Auctions last changed before that are NOT fully represented — raise \"scan_pages\" or set an explicit window to go deeper."
}
}Two consequences to keep in mind:
Name the asset programme when you can.
procedure_type: ["smallPrivatization"]makes the server query the per-type feeds directly, which covers the 100 most recent auctions of each matching selling method instead of whatever happened to be busiest platform-wide.An empty result means "not in the scanned window", not "does not exist." Widen with
scan_pages, or passchanged_sinceto scan a specific historical period.
The feed only runs forward in time from a cursor, so the newest records always sit at the end of a crawl. Starting at an arbitrary "7 days ago" would spend the whole page budget on old records and never reach the present. Instead the crawler walks a short window ending at now and then extends backwards in doubling segments while budget remains — so current auctions are always covered first.
Data notes
Bidder and buyer identities are redacted upstream and appear as
[redacted].Document
downloadUrlvalues are public and can be fetched directly.Bid amounts become visible only after an auction concludes.
auctionIdencodes its programme and publication date:LRE(landRental-english) + serial-UA-+20260708+ serial.
Development
npm run typecheck # tsc --noEmit
npm run build # compile to build/
npm run smoke # build, then exercise all 10 tools against the live APIscripts/smoke.mjs is an integration check, not a unit test — it hits production
Prozorro.Sale and prints a one-line summary per tool.
License
ISC
Available Tools
10 toolsanalyze_auction_marketAggregate statistics over a periodARead-onlyIdempotent
Counts, price statistics and sold-share over a window of auction activity, broken down by a dimension of your choice.
WHEN TO USE: questions about volume and trends rather than individual lots — "how much land was auctioned last week", "which regions are most active", "what share of timber lots actually sell", "who are the biggest sellers".
KEY PARAMETERS
group_by: the breakdown dimension. "direction" (asset programme, default), "sellingMethod", "status", "region" or "seller".
since / until: the period to analyse. Omit both to analyse the most recent activity.
procedure_type / status / region / keyword: narrow the population before aggregating.
scan_pages: default 15. Raise for a larger, more representative sample.
EXAMPLE — which regions had the most land activity recently: {"procedure_type":["landRental","landSell"],"group_by":"region","scan_pages":25}
EXAMPLE — how privatisation performed in July 2026: {"procedure_type":["smallPrivatization"],"since":"2026-07-01","until":"2026-07-31", "group_by":"sellingMethod","scan_pages":30}
RETURNS: totals with count/total/mean/median/min/max starting prices, a status histogram, soldSharePercentOfSettled (settled = complete, unsuccessful or cancelled only), and the same figures per group. CRITICAL: these describe only auctions CHANGED inside the scanned window, not the whole catalogue. Always report the window and coverage alongside any number.
Inputs: since, until, region, status, +4 more.
find_comparable_auctionsBenchmark an auction against similar onesARead-onlyIdempotent
Takes one auction and finds recent comparable ones, then reports median prices and how often that kind of lot actually sells.
WHEN TO USE: valuation and risk questions — "is this price reasonable", "what do similar plots go for", "how likely is this to sell", "should I bid at the starting price".
KEY PARAMETERS
auction (required): the reference auction — public auction id or procedure id.
match_on: what a comparable must share. Default ["sellingMethod","classification"]. sellingMethod — same auction format and programme classification — same CAV asset category region — same oblast; add this for a local benchmark, which is usually what is wanted valueRange — within ±50% of the starting price; use to exclude outliers Adding more criteria gives a tighter but smaller sample.
concluded_only: default true — compares only against finished auctions, which is what a price benchmark needs. Set false to also see what is currently on the market.
limit / scan_pages: widen the sample when comparableCount comes back low.
EXAMPLE — price benchmark for a land lease: {"auction":"LRE001-UA-20260708-03894","match_on":["sellingMethod","classification"]}
EXAMPLE — what similar assets are on the market right now: {"auction":"SPD001-UA-20260806-70620","concluded_only":false,"limit":25}
RETURNS: the reference summary, median starting and achieved prices, sold share, and the comparable auctions themselves. Re-listings of the same lot are excluded so one asset is not counted twice. The sample comes from recent activity, not full history — say so when quoting a figure.
Inputs: auction (required), limit, match_on, scan_pages, +1 more.
get_auctionGet one auction in detailARead-onlyIdempotent
Everything about a single auction: the asset, the financial terms, the seller, and whichever sub-sections are asked for.
WHEN TO USE: the user names an auction, or a search result needs expanding. For deadlines alone use get_auction_timeline; for the outcome alone use get_auction_results — both are much smaller responses.
KEY PARAMETERS
auction (required): public id from the website ("SPD001-UA-20260806-70620") or the internal 24-character procedure id. Both work everywhere.
include: sections to expand. Defaults to ["items","terms"]. items — what is physically being sold: area, cadastral number, address, classification terms — starting price, minimal step, guarantee deposit, registration fee, lease duration, conditions, restrictions documents — attached files with download URLs questions — clarification questions and the seller's answers bids — submitted bids (amounts appear only after the auction concludes) awards — winner determination contracts — signed contracts
EXAMPLE — full picture before deciding whether to bid: {"auction":"SPD001-UA-20260806-70620","include":["items","terms","documents","questions"]}
EXAMPLE — minimal lookup: {"auction":"LRE001-UA-20260708-03894"}
RETURNS: auction summary, seller, description, per-section counts, and the requested sections. Lease auctions additionally carry propertyOwner (the institution the asset belongs to, with its EDRPOU), ownershipType and currentTenants (sitting tenants and their contract dates). Redacted personal data appears as "[redacted]".
Inputs: auction (required), include.
get_auction_documentsAuction documents and download linksARead-onlyIdempotent
Files published for one auction, each with a direct public download URL that can be fetched without authentication.
WHEN TO USE: "show me the documents", "where is the technical specification", "get the signed contract", "is there a photo of the property".
KEY PARAMETERS
auction (required): public auction id or 24-character procedure id.
document_type: case-insensitive substring of the type. Common values: technicalSpecifications, illustration, notice, contractSigned, transferAct, act, cancellationDetails, evaluationCriteria.
include_attachments_of: which sets to return. Defaults to ["auction"]. Add "awards" and "contracts" for outcome paperwork (protocols, signed contracts, transfer acts), "cancellations" for the withdrawal justification.
include_superseded: true to also list earlier revisions of files the seller later replaced. Use when the user asks what changed. Default false — current versions only.
EXAMPLE — just the technical spec: {"auction":"SPD001-UA-20260806-70620","document_type":"technicalSpecifications"}
EXAMPLE — the complete paper trail including the signed contract: {"auction":"SPD001-UA-20260806-70620","include_attachments_of":["auction","awards","contracts"]}
RETURNS: per set, a list of documents with title, type, format, publication date and downloadUrl. Documents attached to bids are never published.
Inputs: auction (required), document_type, include_superseded, include_attachments_of.
get_auction_resultsAuction outcome and final priceARead-onlyIdempotent
How one auction ended: sold or not, for how much, to how many bidders.
WHEN TO USE: "what did it go for", "did it sell", "how many people bid", "why was it cancelled". Works on in-progress auctions too — it reports outcome "in_progress" rather than failing.
KEY PARAMETERS
auction (required): public auction id or 24-character procedure id. No other parameters.
EXAMPLE: {"auction":"SPE001-UA-20260729-69703"}
RETURNS: outcome (contract_signed / winner_determined / ended_without_winner / cancelled_by_seller / in_progress), starting vs final price with priceUpliftPercent between them, bid and disqualified-bid counts, attemptNumber (>1 means the lot failed to sell before), awards, contracts and cancellation reasons. Winner identities are redacted by the platform; bid amounts appear only after the auction concludes.
Inputs: auction (required).
get_auction_timelineAuction schedule and deadlinesARead-onlyIdempotent
The stage clock for one auction: what has passed, what is running now, what comes next, and how much time is left to bid.
WHEN TO USE: any time-related question — "how long do I have", "when is the auction", "has the question period closed", "what happens after bidding". Far smaller than get_auction for this.
KEY PARAMETERS
auction (required): public auction id or 24-character procedure id.
include_revisions: true to also list archived revisions, showing when the seller amended the terms. Use when the user suspects the conditions changed. Default false.
EXAMPLE — "can I still bid on this?": {"auction":"LRE001-UA-20260708-03894"}
EXAMPLE — "did the seller change anything after publishing?": {"auction":"LRE001-UA-20260708-03894","include_revisions":true}
RETURNS: status with its plain-language meaning, every stage marked past/current/upcoming, the next deadline, and a bidding block with closesAt / stillOpen / hoursRemaining. Cancellation reasons appear when the auction was withdrawn.
Inputs: auction (required), include_revisions.
get_publication_constraintsEarliest possible auction date for a new listingARead-onlyIdempotent
Seller-side planning: if a lot is published today, how soon may the auction itself run.
WHEN TO USE: the user is preparing to list something and needs to plan dates — "how far ahead do I need to publish", "what is the minimum notice period", "can we hold the auction before the 20th". This is the only forward-looking tool here; everything else describes auctions that already exist.
KEY PARAMETERS
procedure_type (required): a selling method such as "smallPrivatization-english". A family name such as "smallPrivatization" is also accepted and every format it supports is checked at once, which is useful for comparing notice periods before choosing a format.
EXAMPLE — notice period for one format: {"procedure_type":"landRental-english"}
EXAMPLE — compare every format of a programme: {"procedure_type":"smallPrivatization"}
RETURNS: per selling method, earliestAuctionStart (the soonest auctionPeriod.startDate the platform would accept for a procedure published now) and noticeDays, that gap in days. The value is computed live and moves with the calendar, so it is not cached.
Inputs: procedure_type (required).
list_procedure_typesAsset programmes, auction formats and statusesARead-onlyIdempotent
The vocabulary every other tool filters on. Cheap, cached, no network cost after the first call.
WHEN TO USE: before a search whose asset programme is unclear, or when the user asks what kinds of auctions exist, what a status means, or what an auction id prefix stands for. Call this rather than guessing a procedure_type value — an unrecognised one silently returns nothing.
KEY PARAMETERS
filter: substring to narrow the list, e.g. "land", "lease", "privat", "timber".
include_status_glossary: default true. Set false when only the programme list is needed.
EXAMPLE — what land-related programmes exist: {"filter":"land"}
EXAMPLE — the full vocabulary: {}
RETURNS: 33 programme families, each with its auction formats, the exact sellingMethod values to pass as procedure_type, and the three-letter auction-id prefix each produces (LRE = landRental-english, SPE = smallPrivatization-english, and so on). Plus the auction-id format and, by default, what each of the ten procedure statuses means.
Inputs: filter, include_status_glossary.
search_auctionsSearch Prozorro.Sale auctionsARead-onlyIdempotent
Find auctions of Ukrainian public assets. The entry point for any "what is available" question.
WHEN TO USE: the user describes what they are looking for rather than naming one auction. For a specific auction id, call get_auction instead.
KEY PARAMETERS
procedure_type: name the asset programme whenever the user implies one ("land", "privatisation", "lease"). This switches to per-type feeds and covers far more relevant auctions. Family names ("landRental") expand to every format; exact values ("landRental-english") are used as-is. Call list_procedure_types if unsure of the vocabulary.
open_for_bids: true for "what can I bid on" — keeps only auctions whose deadline has not passed.
keyword: Ukrainian free text over title, description, items, classification, locality. All words must match.
region / classification / min_value / max_value / published_from / published_to: narrowing filters.
seller / seller_edrpou: the body RUNNING the auction (often a regional SPFU office).
property_owner / property_owner_edrpou: the organisation the asset BELONGS to — the university, hospital or school whose premises are leased out. Use this when the user names an institution: on lease auctions the institution is almost never the seller. EDRPOU is exact, prefer it. Published by the legitimatePropertyLease family only; elsewhere owner and seller are the same body.
changed_since + changed_until: scan a specific historical period instead of recent activity.
scan_pages: raise (up to 40) when a broad query comes back thin or truncated.
EXAMPLE — everything Lviv Polytechnic put up for lease this year: {"procedure_type":["legitimatePropertyLease"],"property_owner_edrpou":"02071010", "changed_since":"2026-01-01","changed_until":"2026-08-06","scan_pages":40}
EXAMPLE — property lease near Lviv, still open, under 50 000 UAH: {"procedure_type":["legitimatePropertyLease"],"open_for_bids":true,"region":"Львів","max_value":50000,"limit":10}
EXAMPLE — everything privatisation-related sold in July 2026: {"procedure_type":["smallPrivatization","largePrivatization"],"status":["complete"], "changed_since":"2026-07-01","changed_until":"2026-07-31","scan_pages":25}
RETURNS: compact auction summaries (id, title, status, price, region, seller, propertyOwner, deadlines, auctionUrl) plus a "scanned" block. ALWAYS relay that block's window and truncation to the user — an empty result means "not in the scanned window", never "does not exist".
Inputs: limit, region, seller, status, +14 more.
track_auction_changesWatch for new and updated auctionsARead-onlyIdempotent
What appeared or changed in a niche since a given moment. Cursor-based, so repeated calls make forward progress without re-reading the same activity.
WHEN TO USE: monitoring rather than searching — "anything new since yesterday", "did anything change on the lots I am watching", "keep me posted on timber auctions". For a one-off "what exists" question use search_auctions instead.
KEY PARAMETERS
since: ISO instant to watch from. Defaults to 24 hours ago. On follow-up polls pass back the nextCursor from the previous response — that is the whole point of this tool.
procedure_type / status / keyword / region: narrow the watch to one niche.
limit / scan_pages: raise when a busy window truncates.
EXAMPLE — first poll of a niche: {"procedure_type":["landRental"],"region":"Полтав","limit":20}
EXAMPLE — follow-up poll using the cursor from the previous response: {"procedure_type":["landRental"],"region":"Полтав","since":"2026-08-06T06:27:21.880000Z"}
RETURNS: changed auctions with changedAt and an isNew flag distinguishing brand-new listings from updates to existing ones, a newlyPublished count, and nextCursor for the following poll. The cursor is inclusive, so the last auction may repeat once.
Inputs: limit, since, until, region, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool targets a clearly distinct aspect: searching, viewing details, documents, timeline, results, comparables, monitoring, market stats, vocabulary, and seller constraints. Even related tools like get_auction_timeline and get_auction_results are scoped to different questions.
All tool names follow a consistent verb_noun pattern with lowercase and underscores, using action verbs like search, get, find, track, analyze, list, and get. Sub-resources of an auction are consistently suffixed (get_auction_documents, get_auction_timeline, get_auction_results).
10 tools is well-scoped for a public-asset auction platform. Each tool covers a distinct facet of the domain (search, detail, documents, timeline, results, comparables, monitoring, market analysis, vocabulary, and seller-side planning) without redundancy.
The tool surface covers the full read-side lifecycle: discovering auctions, inspecting any aspect (items, terms, documents, bids, awards, contracts), checking deadlines and outcomes, benchmarking prices, monitoring changes over time, aggregating market statistics, and even planning publication dates. No critical dead ends or missing operations for the server's apparent informational and analytical purpose.
Maintenance
Related MCP Connectors
Prozorro.Sale MCP — Ukraine's state and municipal asset sales and leases (keyless).
ProZorro MCP — Ukraine government procurement (keyless).
Experimental read-only MCP over metadata of Ukrainian court decisions (DSA/EDRSR open data).
MCP server for prozorro_tender_monitor_mcp
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides access to Ukraine's public procurement data (ProZorro) via MCP, keyless and integrated with Pipeworx gateway for AI agents.94 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Cannons Auctions API, enabling natural language access to auction data including item search, auction listings, and detailed item information.2-

vartoofficial
AlicenseNot gradedqualityDmaintenanceMCP server for Ukrainian public procurement (Prozorro) that exposes tools to search tenders, retrieve tender details and cards, list and read tender documents.ISC- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents structured access to Public Procurement Registry data, allowing natural language queries for planned procurements, open tenders, contract awards, buyers, and winning suppliers.MIT