CodePostalPro
REMOTE · API.CODEPOSTALPRO.COM · SCANNED SEP 29
Postal lookups for 120 countries with cited sources; deep US tier: demographics, climate, area codes
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Context-footprint check failed: tool/resource definitions use about 1214 tokens (~173/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the CodePostalPro MCP server?
CodePostalPro is a hosted endpoint at https://api.codepostalpro.com/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 · api.codepostalpro.com
claude mcp add --transport http com-codepostalpro-postal-codes 'https://api.codepostalpro.com/mcp'
{
"mcpServers": {
"com-codepostalpro-postal-codes": {
"url": "https://api.codepostalpro.com/mcp"
}
}
} {
"servers": {
"com-codepostalpro-postal-codes": {
"type": "http",
"url": "https://api.codepostalpro.com/mcp"
}
}
} [mcp_servers.com-codepostalpro-postal-codes] url = "https://api.codepostalpro.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-codepostalpro-postal-codes": {
"type": "remote",
"url": "https://api.codepostalpro.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-codepostalpro-postal-codes --url 'https://api.codepostalpro.com/mcp' --transport streamable-http
mcp_servers:
com-codepostalpro-postal-codes:
url: "https://api.codepostalpro.com/mcp" {
"McpServers": {
"com-codepostalpro-postal-codes": {
"Transport": "http",
"Url": "https://api.codepostalpro.com/mcp"
}
}
} assistant mcp add com-codepostalpro-postal-codes -t streamable-http -u 'https://api.codepostalpro.com/mcp'
{
"mcpServers": {
"com-codepostalpro-postal-codes": {
"type": "http",
"url": "https://api.codepostalpro.com/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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_countries” rewrote its description, which is the text the model reads security
- Tool “lookup_postal_code” rewrote its description, which is the text the model reads security
- Tool “search_places” rewrote its description, which is the text the model reads security
- 22 Sept 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_countries” rewrote its description, which is the text the model reads security
- Tool “search_places” rewrote its description, which is the text the model reads security
- Tool “lookup_postal_code” rewrote its description, which is the text the model reads security
- Schema quality: 149 → 172 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- Tool “area_code_lookup” changed its title: US area code lookup cosmetic
- Tool “get_group” changed its title: City & district details cosmetic
- Tool “get_region” changed its title: Region details cosmetic
- Tool “list_countries” changed its title: Covered countries cosmetic
- Tool “lookup_postal_code” changed its title: Postal code lookup cosmetic
- Tool “nearby_places” changed its title: Nearby postal codes cosmetic
- Tool “search_places” changed its title: Place search cosmetic
- 21 Sept 26 60
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 29 Sept 2026 · Probed https://api.codepostalpro.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=codepostalpro.com | CN=WE1,O=Google Trust Services,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9d68f977f00c6ca30efacc82593f9a25 |
| SANs: codepostalpro.com, api.codepostalpro.com, *.api.codepostalpro.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.codepostalpro.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| codepostalpro.com. | 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://api.codepostalpro.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.codepostalpro.com/mcp | HTTPS enforced | 301 | https://codepostalpro.com/mcp |
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 →
area_code_lookup US area code lookup ~163
Where a US telephone area code is used: the state(s) it serves, the cities with the most ZIPs listing it, total ZIP and city counts, and `overlay_codes` — codes assigned to the same territory (e.g. 310 and 424 in west Los Angeles). Use it for "where is area code 310", "what area code is Denver" (via the city’s ZIPs instead), or to sanity-check a phone number’s geography. Caveat to relay: NANPA assigns codes to rate centres, matched here to cities — city-level accuracy, not a legal boundary, and a mobile number keeps its code when its owner moves.
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | string | yes | Three-digit NANPA area code, e.g. "310" |
No output schema declared.
No examples provided.
get_group City & district details ~115
A city (US), département (France), province (Morocco), post office (Algeria) or delegation (Tunisia) with all its localities / ZIP codes. For a US city this is the complete list of its ZIP codes with coordinates, time zone and area codes. Needs the region slug and the group slug (both from get_region or from any record's `region.slug` / `group.slug`).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| group | string | yes | – |
| region | string | yes | – |
No output schema declared.
No examples provided.
get_region Region details ~106
A state, région, wilaya or governorate with the list of its cities / départements / delegations (names, slugs and their postal codes), plus for US states every telephone area code in use. Use the slugs it returns to call get_group or get_place. Region slugs are lower-case hyphenated names: "texas", "ile-de-france", "alger".
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| region | string | yes | Region slug |
No output schema declared.
No examples provided.
list_countries Covered countries ~85
Coverage overview: the eight curated countries with postal-code format, hierarchy labels (e.g. state › city › ZIP), key facts (capital, population, area, currency, calling code) and time zones — plus `bulk_tier` with per-country postal-code counts for the ~115 additional countries served from GeoNames. Call it once if unsure whether a country is covered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_postal_code Postal code lookup ~315
Look up a postal code or US ZIP code. Returns every locality that carries the code with its city, county/administrative division, region (state, département, wilaya…), coordinates, IANA time zone, US telephone area codes, USDA 2023 plant hardiness / planting zone (e.g. 7b with its temperature band), and US Census demographics (population, density and land area, median household and per-capita income, median age, households, housing units, median home value, median gross rent — measured for the ZCTA, the Census approximation of the ZIP area). Each record lists its `sources` and a `verification` status (cross-checked | source-single | conflict | unverified); on `conflict`, `alternate_codes` gives the competing values and their sources — never pick one silently; tell the user both. Curated coverage (full records): United States (ZIP), Germany, Austria, Spain, France, Algeria, Tunisia, Morocco. All other countries (~115 more: GB, CA, IN, JP, MX, BR…) return bulk-tier records — place name, admin areas and coordinates from GeoNames, marked `tier: "bulk"` and single-source, without demographics.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The postal / ZIP code exactly as written, e.g. "90210", "75001", "16000" |
| country | string | yes | ISO 3166-1 alpha-2 code: US, FR, DZ, TN or MA |
No output schema declared.
No examples provided.
nearby_places Nearby postal codes ~138
List localities around a latitude/longitude, nearest first, each with `distance_km`. Use it for "what ZIP codes are near…", "postal codes within 10 km of…", or to resolve coordinates to the closest postal code (the first result). Distances are to the locality centroid from the source data, not to a boundary.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO code filter |
| lat | number | yes | – |
| limit | integer | – | 1–100, default 20 |
| lon | number | yes | – |
| radius_km | number | – | 0.5–200, default 25 |
No output schema declared.
No examples provided.
search_places Place search ~183
Find localities by name, city name, or the beginning of a postal code. Use this when the user gives a place name and wants its postal code(s), or has a partial code. Results are ranked exact-name-first, then by population. Returns the same full records as lookup_postal_code. Restrict with `country` whenever it is known — names repeat across countries and states (there are many Springfields). With a non-curated `country` (GB, CA, JP…), searches the bulk GeoNames tier by place name or postal-code prefix.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO code to restrict the search (US, FR, DZ, TN, MA) |
| limit | integer | – | Max results, 1–100 (default 20) |
| query | string | yes | Place name or postal-code prefix, at least 2 characters |
No output schema declared.
No examples provided.
What is the CodePostalPro MCP server?
CodePostalPro is an MCP server listed in the public MCP registry as com.codepostalpro/postal-codes. Postal lookups for 120 countries with cited sources; deep US tier: demographics, climate, area codes. This page covers its hosted endpoint (https://api.codepostalpro.com/mcp).
Is the CodePostalPro MCP server safe to use?
CodePostalPro scores 71 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 CodePostalPro MCP server expose?
CodePostalPro exposes 7 tools: lookup_postal_code, search_places, nearby_places, get_region, get_group, and 2 more. Their descriptions and schemas cost roughly 1,105 tokens of context every time the server is loaded.
Does the CodePostalPro MCP server require authentication?
No. We connected to CodePostalPro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CodePostalPro MCP server still maintained?
CodePostalPro is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.