Ziplore: US ZIP Code API (county, time zone, demographics, radius)
REMOTE · ZIPLORE.CYBERMAX-TOOLS.WORKERS.DEV · SCANNED SEP 28
Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 373 tokens (~74/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Ziplore: US ZIP Code API (county, time zone, demographics… MCP server?
Ziplore: US ZIP Code API (county, time zone, demographics… is a hosted endpoint at https://ziplore.cybermax-tools.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ziplore.cybermax-tools.workers.dev
claude mcp add --transport http shawmena-dotcom-zip-data-api 'https://ziplore.cybermax-tools.workers.dev/mcp'
{
"mcpServers": {
"shawmena-dotcom-zip-data-api": {
"url": "https://ziplore.cybermax-tools.workers.dev/mcp"
}
}
} {
"servers": {
"shawmena-dotcom-zip-data-api": {
"type": "http",
"url": "https://ziplore.cybermax-tools.workers.dev/mcp"
}
}
} [mcp_servers.shawmena-dotcom-zip-data-api] url = "https://ziplore.cybermax-tools.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shawmena-dotcom-zip-data-api": {
"type": "remote",
"url": "https://ziplore.cybermax-tools.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add shawmena-dotcom-zip-data-api --url 'https://ziplore.cybermax-tools.workers.dev/mcp' --transport streamable-http
mcp_servers:
shawmena-dotcom-zip-data-api:
url: "https://ziplore.cybermax-tools.workers.dev/mcp" {
"McpServers": {
"shawmena-dotcom-zip-data-api": {
"Transport": "http",
"Url": "https://ziplore.cybermax-tools.workers.dev/mcp"
}
}
} assistant mcp add shawmena-dotcom-zip-data-api -t streamable-http -u 'https://ziplore.cybermax-tools.workers.dev/mcp'
{
"mcpServers": {
"shawmena-dotcom-zip-data-api": {
"type": "http",
"url": "https://ziplore.cybermax-tools.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://ziplore.cybermax-tools.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cybermax-tools.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c35d7b80a04e107b91b8db5035185f9f95 |
| SANs: *.cybermax-tools.workers.dev, cybermax-tools.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ziplore.cybermax-tools.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ziplore.cybermax-tools.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://ziplore.cybermax-tools.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
city_zips ZIP codes of a city ~48
All ZIP codes of a US city, largest population first.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| limit | integer | – | – |
| state | string | – | 2-letter code or name |
No output schema declared.
No examples provided.
nearest_zip Nearest ZIP to a point ~47
Reverse geocode a latitude/longitude to the nearest US ZIP code(s), with distance.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
zip_distance Distance between two ZIPs ~35
Great-circle distance in miles and km between two US ZIP codes.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
zip_lookup Look up US ZIP codes ~101
City, state, county and FIPS, coordinates, time zone with UTC offset, and Census demographics (population, income, home value, rent) for up to 10 US ZIP codes. Accepts ZIP+4, addresses and ZIPs missing a leading zero.
| Name | Type | Req | Description |
|---|---|---|---|
| demographics | boolean | – | – |
| zips | array | yes | US ZIP codes (ZIP+4, addresses and ZIPs that lost their leading zero are accepted). Up to 10. |
No output schema declared.
No examples provided.
zips_in_radius ZIP codes within N miles ~74
Every US ZIP within N miles (max 25) of a ZIP or a lat/lon point, closest first, with distance in miles.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | – |
| limit | integer | – | – |
| lon | number | – | – |
| miles | number | yes | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
What is the Ziplore: US ZIP Code API (county, time zone, demographics… MCP server?
Ziplore: US ZIP Code API (county, time zone, demographics… is an MCP server listed in the public MCP registry as io.github.shawmena-dotcom/zip-data-api. Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key. This page covers its hosted endpoint (https://ziplore.cybermax-tools.workers.dev/mcp).
Is the Ziplore: US ZIP Code API (county, time zone, demographics… MCP server safe to use?
Ziplore: US ZIP Code API (county, time zone, demographics… scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ziplore: US ZIP Code API (county, time zone, demographics… MCP server expose?
Ziplore: US ZIP Code API (county, time zone, demographics… exposes 5 tools: zip_lookup, zips_in_radius, city_zips, nearest_zip, zip_distance. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.
Does the Ziplore: US ZIP Code API (county, time zone, demographics… MCP server require authentication?
No. We connected to Ziplore: US ZIP Code API (county, time zone, demographics… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ziplore: US ZIP Code API (county, time zone, demographics… MCP server still maintained?
Ziplore: US ZIP Code API (county, time zone, demographics… is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.