Remote MCP · Endpoint

Regon Pl MCP server

No. Regon Pl answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/regon-pl/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/regon-pl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
63 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Polish business register (REGON / BIR1.1) — resolve any Polish company by NIP, REGON or KRS number…
Listing
From the official MCP registry (active).
Recent checks of Regon Pl
CheckedResultHandshake
1 hour agoHandshake completed63 ms
2 days agoHandshake completed155 ms
4 days agoHandshake completed87 ms
6 days agoHandshake completed300 ms
7 days agoHandshake completed49 ms
9 days agoHandshake completed62 ms
10 days agoHandshake completed212 ms
11 days agoHandshake completed69 ms
14 days agoHandshake completed46 ms
16 days agoHandshake completed42 ms
17 days agoHandshake completed61 ms
19 days agoHandshake completed71 ms
20 days agoHandshake completed42 ms
21 days agoHandshake completed48 ms
22 days agoHandshake completed63 ms
23 days agoHandshake completed42 ms

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

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