Ext Ops Panel
Open dashboard
Comparison

Ziplore: US ZIP Code API (county, time zone, demographics, radius) vs loc8n Geographic Data

Ziplore: US ZIP Code API (county, time zone, demographics, radius) is an MCP server published by CyberMax-tools. Marketplaces we read that list it: 1 (Official MCP Registry). loc8n Geographic Data is an MCP server published by gener8v-thomas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceZiplore: US ZIP Code API (county, time zone, demographics, radius)loc8n Geographic Data
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Ziplore: US ZIP Code API (county, time zone, demographics, radius) vs loc8n Geographic Data
FactZiplore: US ZIP Code API (county, time zone, demographics, radius)loc8n Geographic Data
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (ziplore.cybermax-tools.workers.dev/mcp)Remote server (mcp.loc8n.com/sse)
Transport (differs)Streamable HTTPSSE
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/cybermax-tools/product-factorygithub.com/gener8v/gener8v.mcp.geographic-data
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agoNot responding since 2026-10-14

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

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

In its own words, on Official MCP Registry:

Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key.

loc8n Geographic Data

In its own words, on Official MCP Registry:

U.S. demographics, housing, mortgage, migration, and employment data via loc8n API

How to run each

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

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

loc8n Geographic Data As a remote MCP server

Claude Code
claude mcp add --transport sse mcp-geographic-data https://mcp.loc8n.com/sse --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: LOC8N_API_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of Ziplore: US ZIP Code API (county, time zone, demographics, radius) responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Ziplore: US ZIP Code API (county, time zone, demographics, radius) publish no settings it asks for, so we do not compare settings.

What it can do: Ziplore: US ZIP Code API (county, time zone, demographics, radius) · What it can do: loc8n Geographic Data · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built