Remote MCP · Endpoint

Zippopotam MCP server

No. Zippopotam answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/zippopotam/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/zippopotam
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
42 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Zippopotam MCP — wraps Zippopotam.us ZIP/postal code API (free, no auth)
Listing
From the official MCP registry (active).
Recent checks of Zippopotam
CheckedResultHandshake
1 hour agoHandshake completed62 ms
2 days agoHandshake completed65 ms
4 days agoHandshake completed67 ms
6 days agoHandshake completed54 ms
7 days agoHandshake completed75 ms
8 days agoHandshake completed49 ms
9 days agoHandshake completed72 ms
12 days agoHandshake completed42 ms
14 days agoHandshake completed48 ms
15 days agoHandshake completed111 ms
17 days agoHandshake completed60 ms
18 days agoHandshake completed49 ms
19 days agoHandshake completed39 ms
20 days agoHandshake completed44 ms
21 days agoHandshake completed45 ms
21 days agoHandshake completed47 ms
23 days agoHandshake completed47 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 Zippopotam and makes no claim about it beyond what these checks measured.