_ registry / mcp streamable-http · checked 2h ago

codepostalpro

https://api.codepostalpro.com

Registry code: 1b08d125987913fe

api record

Postal and ZIP code reference. Curated tier (full sourced records with US demographics, climate, area codes…): United States, Germany, Austria, Spain, France, Algeria, Tunisia, Morocco. Bulk tier (place, admin areas, coordinates from GeoNames): ~115 more countries — every populated country with postal codes in GeoNames. Every record carries `sources`, `verification` and its tier; when you relay a value, say where it came from. Data page: https://codepostalpro.com/data-sources/

endpoint
https://api.codepostalpro.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is codepostalpro live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is codepostalpro free to use?
Yes — the hub reached it with no key and no payment.
What tools does codepostalpro have?
7 tools: search_places, get_region, nearby_places, lookup_postal_code, get_group, area_code_lookup, list_countries.
Is codepostalpro safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.8%· all time 99.8%

latency
835ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 428 checks · signed record
  • degraded → live
_ what it is for
used for
  • look up a postal code
  • find places near a coordinate
  • look up a us area code
  • search localities by name
takes → gives
text → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
1 open 6 never probed 1 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_countries reads open 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_places reads unknown 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Max results, 1–100 (default 20)"
        },
        "query": {
          "type": "string",
          "description": "Place name or postal-code prefix, at least 2 characters"
        },
        "country": {
          "type": "string",
          "description": "Optional ISO code to restrict the search (US, FR, DZ, TN, MA)"
        }
      }
    }
    arguments 20 lines
  • get_region reads unknown 20h ago

    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".

    mcp-tool

    {
      "type": "object",
      "required": [
        "country",
        "region"
      ],
      "properties": {
        "region": {
          "type": "string",
          "description": "Region slug"
        },
        "country": {
          "type": "string"
        }
      }
    }
    arguments 16 lines
  • nearby_places reads unknown 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lat",
        "lon"
      ],
      "properties": {
        "lat": {
          "type": "number"
        },
        "lon": {
          "type": "number"
        },
        "limit": {
          "type": "integer",
          "description": "1–100, default 20"
        },
        "country": {
          "type": "string",
          "description": "Optional ISO code filter"
        },
        "radius_km": {
          "type": "number",
          "description": "0.5–200, default 25"
        }
      }
    }
    arguments 27 lines
  • lookup_postal_code reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country",
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "The postal / ZIP code exactly as written, e.g. \"90210\", \"75001\", \"16000\""
        },
        "country": {
          "type": "string",
          "description": "ISO 3166-1 alpha-2 code: US, FR, DZ, TN or MA"
        }
      }
    }
    arguments 17 lines
  • get_group reads unknown 10h ago

    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`).

    mcp-tool

    {
      "type": "object",
      "required": [
        "country",
        "region",
        "group"
      ],
      "properties": {
        "group": {
          "type": "string"
        },
        "region": {
          "type": "string"
        },
        "country": {
          "type": "string"
        }
      }
    }
    arguments 19 lines
  • area_code_lookup reads unknown 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "area_code"
      ],
      "properties": {
        "area_code": {
          "type": "string",
          "description": "Three-digit NANPA area code, e.g. \"310\""
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1b08d125987913fe.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1b08d125987913fe/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1b08d125987913fe/badge.svg)](https://brick.blue/agent/1b08d125987913fe?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.