Is public_data_ukraine_mcp live?

Yes — it answered the hub's last check (checked 45m ago). It answered 100% of checks over the last 30 days.

Is public_data_ukraine_mcp free to use?

No — it charges per call, from 0 USDC, quoted in its own 402 answers.

What tools does public_data_ukraine_mcp have?

5 tools: get_weather_ukraine, search_prozorro_tenders, geocode_ukraine, health_check, get_exchange_rates.

Is public_data_ukraine_mcp safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 45m ago

public_data_ukraine_mcp

https://public-data-ukraine-mcp.mcpize.run

Registry code: 8cbdff06dc119a33

api record

Ukrainian public data — NBU rates, Prozorro, OSM geocoding. Zero auth.

endpoint: https://public-data-ukraine-mcp.mcpize.run/mcp/v1
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is public_data_ukraine_mcp live?: Yes — it answered the hub's last check (checked 45m ago). It answered 100% of checks over the last 30 days.
Is public_data_ukraine_mcp free to use?: No — it charges per call, from 0 USDC, quoted in its own 402 answers.
What tools does public_data_ukraine_mcp have?: 5 tools: get_weather_ukraine, search_prozorro_tenders, geocode_ukraine, health_check, get_exchange_rates.
Is public_data_ukraine_mcp safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

523ms

last good check

priced tools

of 5 tools

_ answered our checks, 90 days 593 checks · signed record

2026-10-12 10:58 down → live
2026-09-27 16:03 unknown → live

_ what it is for

topic: government & legal public records & government
used for: search ukrainian public tenders
get nbu exchange rates
geocode a ukrainian address
get weather for a ukrainian city
takes → gives: text → data
tools: 5 reads

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 5 tools

5 paid 5 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_weather_ukraine reads 0.01 USDC paid 7h ago
Get current weather for Ukrainian city using Open-Meteo (free, no auth). Returns: {temperature_c, windspeed, weathercode, city}

mcp-tool
{ "type": "object", "title": "get_weather_ukraineArguments", "required": [ "city" ], "properties": { "city": { "type": "string", "title": "City" } } }
arguments 13 lines

search_prozorro_tenders reads 0 USDC paid 11h ago

Search Ukrainian public procurement tenders on Prozorro. Returns: {tenders: [{title, value, status, date_modified}]}

mcp-tool

{
  "type": "object",
  "title": "search_prozorro_tendersArguments",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    }
  }
}

arguments 18 lines

geocode_ukraine reads paid never probed
Geocode Ukrainian address to coordinates using OpenStreetMap Nominatim. Returns: {lat, lon, display_name, region, city}

mcp-tool
{ "type": "object", "title": "geocode_ukraineArguments", "required": [ "address" ], "properties": { "address": { "type": "string", "title": "Address" } } }
arguments 13 lines
health_check reads 0 USDC paid 11h ago
Server health check.

mcp-tool
{ "type": "object", "title": "health_checkArguments", "properties": {} }
arguments 5 lines

get_exchange_rates reads 0.01 USDC paid 11h ago

Get official NBU (National Bank of Ukraine) exchange rates. date format: YYYYMMDD or None for today. Returns: {rates, date, source}

mcp-tool

{
  "type": "object",
  "title": "get_exchange_ratesArguments",
  "properties": {
    "date": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Date",
      "default": null
    }
  }
}

arguments 18 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8cbdff06dc119a33.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8cbdff06dc119a33/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/8cbdff06dc119a33/badge.svg)](https://brick.blue/agent/8cbdff06dc119a33?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on mcpize.run 47 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

data-compute-stats-mcp.mcpize.run data_compute_stats_mcp mcp · 6 tools
text-intelligence-mcp.mcpize.run text_intelligence_mcp mcp · 6 tools
docforged.mcpize.run docforge mcp · 5 tools
htmlpdf-transform-mcp.mcpize.run html_transform_mcp mcp · 5 tools
leaseiq-pro.mcpize.run leaseiq-pro via MCPize mcp · 5 tools
web-content-extract-mcp.mcpize.run web_extract_mcp mcp · 5 tools
finance-fintech-mcp.mcpize.run finance_fintech_mcp mcp · 4 tools
marketing-mcp.mcpize.run marketing_mcp mcp · 4 tools

39 more sit on this domain. All of them.