# Ukraine Public Spending

> Ukraine public spending MCP — State Treasury payment transactions (keyless).

- name: io.github.pipeworx-io/ukraine-public-spending
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 96/100
- quality: –/100 (not scored)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fukraine-public-spending
- tools: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fukraine-public-spending/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "ukraine-public-spending": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/ukraine-public-spending/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 98
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-96% +updated-12d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality –/100 (not scored)

Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: n/a (weight 30)

- n/a `tools.descriptions`, `tools.description_length`, `tools.schemas`, `tools.annotations`, `tools.directory_hints`, `tools.token_cost`, `tools.api_dump`: tool list unknown (behind auth, not probed, or empty)

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool list unknown

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: unknown
- tools last changed: 2026-10-18T06:38:47.897Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.pipeworx-io/ukraine-public-spending.svg)](https://protogrid.dev/servers/io.github.pipeworx-io/ukraine-public-spending)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-18 `ua_spend_prozorro_link` removed
  - 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.
- 2026-10-18 `ua_spend_between` removed
  - 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.
- 2026-10-18 `ua_spend_payments` removed
  - 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.
- 2026-10-18 `forget` removed
  - Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
- 2026-10-18 `recall` removed
  - Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.
- 2026-10-18 `remember` removed
  - Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.
- 2026-10-18 `pipeworx_feedback` removed
  - Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
- 2026-10-18 `scan_competitor_ai_presence` removed
  - Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity.
- 2026-10-18 `ai_visibility_check` removed
  - Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns per-model {score, confidence, signals, raw_response} + a combined view. Useful for AI-marketing audits, pre-launch brand checks, competitive monitoring.
- 2026-10-18 `generate_llms_txt` removed
  - Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.

Full history: https://api.protogrid.dev/v1/servers/io.github.pipeworx-io%2Fukraine-public-spending/changes

## Remotes

- https://gateway.pipeworx.io/ukraine-public-spending/mcp (streamable-http, auth none, reachable true, uptime30d 0.95555556)

## Packages

_none_

## Tools (0)

_none observed_