Remote MCP · Endpoint

Prozorro Sale MCP server

No. Prozorro Sale answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/prozorro-sale/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/prozorro-sale
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
164 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Prozorro.Sale MCP — Ukraine's state and municipal asset sales and leases (keyless).
Listing
From the official MCP registry (active).
Recent checks of Prozorro Sale
CheckedResultHandshake
1 hour agoHandshake completed164 ms
1 day agoHandshake completed102 ms
2 days agoHandshake completed98 ms
2 days agoHandshake completed61 ms
4 days agoHandshake completed127 ms
6 days agoHandshake completed268 ms
9 days agoHandshake completed86 ms
11 days agoHandshake completed203 ms
14 days agoHandshake completed107 ms
16 days agoHandshake completed877 ms
18 days agoHandshake completed85 ms
20 days agoHandshake completed2.58 s
22 days agoHandshake completed98 ms
24 days agoHandshake completed61 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Prozorro Sale and makes no claim about it beyond what these checks measured.