Remote MCP · Endpoint

Ziplore: US ZIP Code API (county, time zone, demographics, radius) MCP server

No. Ziplore: US ZIP Code API (county, time zone, demographics, radius) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ziplore.cybermaxtools.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/ziplore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
492 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Ziplore: US ZIP Code API (county, time zone, demographics, radius)
CheckedResultHandshake
1 hour agoHandshake completed492 ms
1 day agoHandshake completed607 ms
2 days agoHandshake completed349 ms
3 days agoHandshake completed600 ms
4 days agoHandshake completed364 ms
5 days agoHandshake completed367 ms
7 days agoHandshake completed635 ms
10 days agoHandshake completed552 ms
12 days agoHandshake completed85 ms
14 days agoHandshake completed376 ms
17 days agoHandshake completed70 ms
19 days agoHandshake completed418 ms
21 days agoHandshake completed589 ms
23 days agoHandshake completed561 ms
25 days agoHandshake completed48 ms

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

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 Ziplore: US ZIP Code API (county, time zone, demographics, radius) and makes no claim about it beyond what these checks measured.