Skip to content
CodePostalPro logo

CodePostalPro

Looks up postal codes and localities by city or region across countries, and serves the same reference data through an API.
At a glanceswept Oct 12, 2026

not read yet

Use

For
People who need to look up postal or zip codes for cities and localities in supported countries
Runs as
API
Used for
  • look up postal codes by city or locality
  • browse postal code and locality counts by country
  • query postal and geographic data through a free API
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (1 in the registry)public registry →
How a program reaches itfound, not claimed · read Oct 15, 2026
  • MCP servercom.codepostalpro/postal-codesverified in the MCP registry
  • Stateanswers, 7 toolschecked 2026-10-15
  • Address to connectapi.codepostalpro.com/mcp
  • API docscodepostalpro.com/apithe vendor's page ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare CodePostalPro with

Pick up to two.

All Developer tools tools →

From people who use itnot part of the reading

No notes yet. What do you use CodePostalPro for?

Sign in to leave a note
Questions this page answers
  • What is CodePostalPro?

    Looks up postal codes and localities by city or region across countries, and serves the same reference data through an API. It is listed in the Atlas under Developer tools.

  • Who is CodePostalPro for?

    People who need to look up postal or zip codes for cities and localities in supported countries

  • Do people use CodePostalPro?

    Little sign of use.

  • What are alternatives to CodePostalPro?

    In Developer tools, by use: Coddy, World Monitor, IO Tools, Better i18n, MCP Analytics, Albato.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.