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 2 days ago.

UpLast checked 2 days ago

Server URL

https://ziplore.cybermax-tools.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.shawmena-dotcom/zip-data-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
434 ms
Tools exposed
5 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key.
Website
https://ziplore.cybermax-tools.workers.dev/
Repository
https://github.com/shawmena-dotcom/product-factory
Listing
From the official MCP registry (active).
Recent checks of Ziplore: US ZIP Code API (county, time zone, demographics, radius)
CheckedResultHandshake
2 days agoHandshake completed434 ms
3 days agoHandshake completed547 ms
3 days agoHandshake completed652 ms
5 days agoHandshake completed561 ms
6 days agoHandshake completed467 ms
7 days agoHandshake completed335 ms
8 days agoHandshake completed431 ms
9 days agoHandshake completed574 ms
11 days agoHandshake completed1.07 s
14 days agoHandshake completed644 ms
16 days agoHandshake completed386 ms
18 days agoHandshake completed376 ms
21 days agoHandshake completed883 ms
22 days agoHandshake completed99 ms
25 days agoHandshake completed374 ms
27 days agoHandshake completed469 ms
29 days agoFailed - the check failed for an unclassified reason—
30 days agoHandshake completed347 ms
32 days agoHandshake completed668 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.