Ziplore: US ZIP Code API (county, time zone, demographics, radius) is an MCP server published by io.github.CyberMax-tools, hosted at ziplore.cybermax-tools.workers.dev. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 5 tools, including zip_lookup, zips_in_radius, city_zips, nearest_zip, zip_distance.
Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key.
70 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| zips * | array | US ZIP codes (ZIP+4, addresses and ZIPs that lost their leading zero are accepted). Up to 10. |
| demographics | boolean |
{
"name": "zip_lookup",
"title": "Look up US ZIP codes",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"zips"
],
"properties": {
"zips": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 10,
"minItems": 1,
"description": "US ZIP codes (ZIP+4, addresses and ZIPs that lost their leading zero are accepted). Up to 10."
},
"demographics": {
"type": "boolean",
"default": true
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Every US ZIP within N miles (max 25) of a ZIP or a lat/lon point, closest first, with distance in miles.
| Parameter | Type | Description |
|---|---|---|
| lat | number | |
| lon | number | |
| zip | string | |
| limit | integer | |
| miles * | number |
{
"name": "zips_in_radius",
"title": "ZIP codes within N miles",
"description": "Every US ZIP within N miles (max 25) of a ZIP or a lat/lon point, closest first, with distance in miles.",
"inputSchema": {
"type": "object",
"required": [
"miles"
],
"properties": {
"lat": {
"type": "number"
},
"lon": {
"type": "number"
},
"zip": {
"type": "string"
},
"limit": {
"type": "integer",
"default": 25,
"maximum": 50,
"minimum": 1
},
"miles": {
"type": "number",
"maximum": 25,
"minimum": 0.1
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}All ZIP codes of a US city, largest population first.
| Parameter | Type | Description |
|---|---|---|
| city * | string | |
| limit | integer | |
| state | string | 2-letter code or name |
{
"name": "city_zips",
"title": "ZIP codes of a city",
"description": "All ZIP codes of a US city, largest population first.",
"inputSchema": {
"type": "object",
"required": [
"city"
],
"properties": {
"city": {
"type": "string"
},
"limit": {
"type": "integer",
"default": 25,
"maximum": 50,
"minimum": 1
},
"state": {
"type": "string",
"description": "2-letter code or name"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Reverse geocode a latitude/longitude to the nearest US ZIP code(s), with distance.
| Parameter | Type | Description |
|---|---|---|
| lat * | number | |
| lon * | number | |
| count | integer |
{
"name": "nearest_zip",
"title": "Nearest ZIP to a point",
"description": "Reverse geocode a latitude/longitude to the nearest US ZIP code(s), with distance.",
"inputSchema": {
"type": "object",
"required": [
"lat",
"lon"
],
"properties": {
"lat": {
"type": "number"
},
"lon": {
"type": "number"
},
"count": {
"type": "integer",
"default": 1,
"maximum": 10,
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Great-circle distance in miles and km between two US ZIP codes.
| Parameter | Type | Description |
|---|---|---|
| to * | string | |
| from * | string |
{
"name": "zip_distance",
"title": "Distance between two ZIPs",
"description": "Great-circle distance in miles and km between two US ZIP codes.",
"inputSchema": {
"type": "object",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string"
},
"from": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Ziplore answers US ZIP code questions from an in-memory Census/GeoNames table. zip_lookup for facts and demographics, zips_in_radius for nearby ZIPs, city_zips for a city's ZIPs, nearest_zip for a lat/lon, zip_distance for miles between two ZIPs. Cite meta.attribution.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.