Remote MCP · Endpoint

PackZoo MCP server

No. PackZoo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://packzoo.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.IAfanasov/packzoo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
4.02 s
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Compare parcel and letter delivery prices across 60+ carriers in 27 European countries.
Listing
From the official MCP registry (active).
Recent checks of PackZoo
CheckedResultHandshake
1 hour agoHandshake completed4.02 s
2 days agoHandshake completed276 ms
4 days agoHandshake completed142 ms
5 days agoHandshake completed244 ms
7 days agoHandshake completed89 ms
8 days agoHandshake completed456 ms
9 days agoHandshake completed235 ms
12 days agoHandshake completed92 ms
13 days agoHandshake completed117 ms
15 days agoHandshake completed76 ms
17 days agoHandshake completed406 ms
18 days agoHandshake completed103 ms
19 days agoHandshake completed94 ms
20 days agoHandshake completed1.30 s
20 days agoHandshake completed1.23 s
21 days agoHandshake completed160 ms
23 days agoHandshake completed227 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 PackZoo and makes no claim about it beyond what these checks measured.