# Ukraine Public Spending (npm · @pipeworx/mcp-ukraine-public-spending)

Ukraine public spending MCP — State Treasury payment transactions (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-ukraine-public-spending/ukraine-public-spending-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ukraine-public-spending/ukraine-public-spending-mcp)
- npm · `@pipeworx/mcp-ukraine-public-spending`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ukraine-public-spending/pipeworx-mcp-ukraine-public-spending.md), [page](https://verifymcp.io/servers/pipeworx-io-ukraine-public-spending/pipeworx-mcp-ukraine-public-spending)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ukraine-public-spending`
- Version: `0.2.0`
- 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-ukraine-public-spending).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 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 (good).
  - 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.
  - 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 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.

### Claude

```bash
claude mcp add pipeworx-io-ukraine-public-spending -- npx -y @pipeworx/mcp-ukraine-public-spending
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-ukraine-public-spending -- npx -y @pipeworx/mcp-ukraine-public-spending
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ukraine-public-spending --command npx --arg -y --arg @pipeworx/mcp-ukraine-public-spending
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, +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.

### 2026-11-02 (score 80, +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.

### 2026-10-31 (score 79, +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.

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

First indexed and scored.

## MCP tools (3)

### `ua_spend_payments` (~433 tokens)

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.

Input parameters:

- `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.

### `ua_spend_between` (~258 tokens)

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.

Input parameters:

- `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, required): Payer (spending body) EDRPOU code, e.g. "26510514".
- `recipient_edrpou` (string, required): Recipient (payee) EDRPOU code, e.g. "37988155".

### `ua_spend_prozorro_link` (~293 tokens)

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.

Input parameters:

- `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, required): Supplier (payment recipient / ProZorro tenderer) EDRPOU code, 8 digits, e.g. "37988155".

## Diagnostics

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

## Score history

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

## Common questions

### 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.

## Links

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