ng-postcode
Related Servers
Alternatives to ng-postcode
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that resolves postal/ZIP codes to place names, states, and coordinates using Zippopotam.us. Free, no API key required.1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for querying Brazilian postal codes (CEP) from the official Correios source, supporting read-only lookups via natural language in any MCP-compatible client.MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for Australian address search and validation powered by Addressr.11 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.69 npm1MIT

io.github.stucchi/italyofficial
AlicenseNot gradedqualityDmaintenanceMCP server exposing Italian open data (municipalities, provinces, regions, postal codes, coordinates, geographic data) through simple, developer-friendly tools.1MIT- AlicenseNot gradedqualityCmaintenanceMCP server for querying Brazilian postal codes (CEP) and territorial areas using official Correios data, providing a read-only tool to complete CEP information.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct input/output: autocomplete (partial->completions), validate (offline structure), lookup (assignment + address), find_postcode_at_location (coords->postcode), resolve_address (address text->postcode). The only mild overlap is validate vs lookup, but descriptions explicitly contrast them (offline structural check vs assignment confirmation).
All names are snake_case with a verb_noun feel (autocomplete_postcode, lookup_postcode, validate_postcode, resolve_address). find_postcode_at_location is longer and inserts a preposition, a minor deviation, but still readable and consistent in style.
Five tools is well-scoped for a postcode service, covering forward lookup, reverse lookup, validation, autocomplete, and address resolution with no redundancy or filler.
The surface covers the main lifecycle: autocomplete, validate, lookup, coordinate->postcode, and address->postcode. Minor gaps exist (e.g. no batch lookup or postcode->coordinate reverse), but core workflows are covered.