@pipeworx/ukraine-public-spending

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/ukraine-public-spending’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

Ukrainian State Treasury payment transactions from spending.gov.ua: who a public body paid, which public bodies paid a supplier, how much and for what, by EDRPOU code. Links a supplier’s payments to its ProZorro tenders as labelled candidates.

Tools

• ua_spend_payments(recipient_edrpou?, payer_edrpou?, date_from?, date_to?, purpose_contains?, limit?): every Treasury payment to and/or from the given EDRPOU codes in a window of up to 92 days. Returns totals, top payers and recipients, and the newest rows (date, amount in UAH, both parties, purpose text, budget and KEKV codes, contract number when recorded).
• ua_spend_between(payer_edrpou, recipient_edrpou, date_from?, date_to?, limit?): payments from one payer to one recipient. Returns found true/false, count, total, a per-month breakdown and the rows. found:false carries data_as_of and a note that the open portal withholds some payers.
• ua_spend_prozorro_link(supplier_edrpou, date_from?, date_to?, max_payers?): the supplier’s Treasury receipts, plus, for each of its largest payers, the ProZorro tenders where that payer was the buyer and the supplier took part. Each link is labelled candidate, because a shared counterparty does not prove which contract a payment settles.

Auth

Keyless.

Data sources

• https://api.spending.gov.ua/api/v2/api/transactions/: State Treasury Service of Ukraine (ДКСУ) payment transactions, the API behind spending.gov.ua.
• https://prozorro.gov.ua/api/search/tenders (POST): ProZorro’s public tender search index, used by ua_spend_prozorro_link.

Things measured live on 2026-10-08:

• payers_edrpous / recipt_edrpous take comma-separated codes; at least one is required, and both together act as an AND.
• A window longer than 92 days is a 400 with a Ukrainian message. Dates must be YYYY-MM-DD.
• Rows run about 2 days behind today.
• Payments to private individuals have the recipient code masked as xxxxxxxxxx by the Treasury, and digits in purpose text masked as xxxx.
• Some payers (for example the Ministry of Defence, 00034022) return an empty list for windows where they certainly paid. Treat empty as “not published”, not “no payment”.
• The first HTTPS request from a cold Cloudflare Worker can get a 525 from the origin. The pack retries once, then falls back to plain HTTP.
• ProZorro’s search rows carry the buyer’s name but never its EDRPOU, so the link tool queries tenderer + buyer together for each payer rather than comparing codes. The tenderer filter on its own is fuzzy.

Tools

• ua_spend_payments — Ukrainian public-money payments from the State Treasury (spending.gov.ua, keyless): every treasury payment made BY a payer EDRPOU and/or TO a recipient EDRPOU in a date window of up to 92 days. Each r
• ua_spend_between — Payments from ONE Ukrainian public payer to ONE recipient (both by EDRPOU) in a window of up to 92 days, from State Treasury data on spending.gov.ua (keyless). Returns found true/false, payment count,
• ua_spend_prozorro_link — Line up a Ukrainian supplier’s State Treasury receipts (spending.gov.ua) with its ProZorro procurement tenders, by supplier EDRPOU. Returns the public bodies that paid the supplier in the window (coun