Remote MCP · Endpoint

PESEL/NIP/REGON Validator MCP server

No. PESEL/NIP/REGON Validator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://apished.com/mcp/v1/idvalidate

The last check completed an MCP handshake.

Registry name
com.apished/pesel-nip-regon-validator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
356 ms
Tools exposed
3 tools
Uptime, last 30 days
64.7% from 17 checks
Described by its publisher as
Validates Polish PESEL, NIP, and REGON checksums; PESEL also decodes birth date and sex.
Listing
From the official MCP registry (active).
Recent checks of PESEL/NIP/REGON Validator
CheckedResultHandshake
1 hour agoHandshake completed356 ms
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed412 ms
13 days agoHandshake completed357 ms
15 days agoHandshake completed397 ms
16 days agoHandshake completed319 ms
17 days agoHandshake completed114 ms
18 days agoHandshake completed115 ms
19 days agoHandshake completed114 ms
20 days agoHandshake completed114 ms
21 days agoHandshake completed113 ms
23 days agoHandshake completed113 ms

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

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 PESEL/NIP/REGON Validator and makes no claim about it beyond what these checks measured.