Remote MCP · Endpoint

IleZa.pl MCP server

No. IleZa.pl answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://ileza.pl/mcp

The last check completed an MCP handshake.

Registry name
io.github.bahdanhal/ileza
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
425 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Editorial fair prices for products in Poland, plus a Polish net salary and tax calculator.
Listing
From the official MCP registry (active).
Recent checks of IleZa.pl
CheckedResultHandshake
7 hours agoHandshake completed425 ms
4 days agoHandshake completed415 ms
14 days agoHandshake completed452 ms
15 days agoHandshake completed403 ms
15 days agoHandshake completed356 ms
17 days agoHandshake completed372 ms
18 days agoHandshake completed369 ms
19 days agoHandshake completed381 ms
20 days agoHandshake completed410 ms
21 days agoHandshake completed399 ms
23 days agoHandshake completed355 ms
26 days agoHandshake completed367 ms
28 days agoHandshake completed417 ms

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

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 IleZa.pl and makes no claim about it beyond what these checks measured.