Ukraine Public Spending
NPM · @PIPEWORX/MCP-UKRAINE-PUBLIC-SPENDING · 2 COMPONENTS
Ukraine public spending MCP — State Treasury payment transactions (keyless).
Available components
Last scanned (7 hours ago)
Scores higher than 68% of npm 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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ukraine-public-spending). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1043 tokens (~347/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-ukraine-public-spending@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-ukraine-public-spending |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ukraine-public-spending/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560778585 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a3604355c8f8993c3ca0e2ffcc47d43107560bfeb6a076b2d452f94b86e55ff1470d185658301a6825e975f392aeaaa9ff35b83cc9babcade27debc7f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
ua_spend_between ~258
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, total UAH, a per-month breakdown, and the payment rows with purpose text and any recorded contract number. found:false means the Treasury published no payment between the two in that window — not proof none was made (some payers, e.g. defence, are withheld). Use to check whether and how much a specific public body paid a specific supplier.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Window start, YYYY-MM-DD. Default: 30 days before date_to. |
| date_to | string | – | Window end, YYYY-MM-DD. Default: today. Window may not exceed 92 days. |
| limit | number|string | – | Rows to return, newest first (1-500). Default 100. |
| payer_edrpou | string | yes | Payer (spending body) EDRPOU code, e.g. "26510514". |
| recipient_edrpou | string | yes | Recipient (payee) EDRPOU code, e.g. "37988155". |
No output schema declared.
No examples provided.
ua_spend_payments ~433
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 row has transaction date, amount (UAH), payer name + EDRPOU, recipient name + EDRPOU, payment purpose text (Ukrainian), budget code, KEKV economic code, and the contract number when the Treasury recorded one. Returns totals and top counterparties across the whole window plus the newest `limit` rows. Use for: who a city council or ministry paid, which public bodies paid a supplier, and what for. Payments to private individuals arrive with the code masked by the Treasury. For payer->recipient pairs use ua_spend_between; to line payments up with ProZorro tenders use ua_spend_prozorro_link.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Window start, YYYY-MM-DD. Default: 30 days before date_to. Window may not exceed 92 days. |
| date_to | string | – | Window end, YYYY-MM-DD. Default: today. |
| limit | number|string | – | Rows to return, newest first (1-500). Default 50. Totals always cover every row in the window. |
| payer_edrpou | string | – | Payer (spending body) EDRPOU code (8-digit Ukrainian legal-entity id; public bodies often 8 digits with leading zeros, e.g. "26510514" for Dnipro City Council). Several may be comma-separated. |
| purpose_contains | string | – | Optional case-insensitive substring filter on the payment purpose text (Ukrainian, e.g. "харчування", "ремонт"). |
| recipient_edrpou | string | – | Recipient (payee) EDRPOU code (8-digit Ukrainian legal-entity id; public bodies often 8 digits with leading zeros, e.g. "26510514" for Dnipro City Council). Several may be comma-separated. |
No output schema declared.
No examples provided.
ua_spend_prozorro_link ~293
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 (count, total UAH), the supplier's ProZorro tenders (tenderID, title, buyer + buyer EDRPOU, value, status), and, for each of the largest payers, the ProZorro tenders where that payer was the buyer and this supplier took part — returned as CANDIDATE links. A shared counterparty does not prove which contract a payment settles — every link is labelled candidate, with the matching basis stated. Use for supplier due diligence across procurement and actual payments. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Payment window start, YYYY-MM-DD. Default: 90 days before date_to. |
| date_to | string | – | Payment window end, YYYY-MM-DD. Default: today. Window may not exceed 92 days. |
| max_payers | number|string | – | How many of the largest payers (by UAH in the window) to check against ProZorro, 1-8. Default 5. |
| supplier_edrpou | string | yes | Supplier (payment recipient / ProZorro tenderer) EDRPOU code, 8 digits, e.g. "37988155". |
No output schema declared.
No examples provided.
How do I install the Ukraine Public Spending MCP server?
Ukraine Public Spending runs locally as an npm package, launched with npx -y @pipeworx/mcp-ukraine-public-spending. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-ukraine-public-spending
claude mcp add pipeworx-io-ukraine-public-spending -- npx -y @pipeworx/mcp-ukraine-public-spending
What is the Ukraine Public Spending MCP server?
Ukraine Public Spending is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ukraine-public-spending. Ukraine public spending MCP, State Treasury payment transactions (keyless). This page covers its npm package (@pipeworx/mcp-ukraine-public-spending).
Is the Ukraine Public Spending MCP server safe to use?
Ukraine Public Spending 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 Ukraine Public Spending MCP server expose?
Ukraine Public Spending exposes 3 tools: ua_spend_payments, ua_spend_between, ua_spend_prozorro_link. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.
Is the Ukraine Public Spending MCP server still maintained?
Ukraine Public Spending 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 Ukraine Public Spending MCP server under?
Ukraine Public Spending declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.