MCP-Geocoder

Conversation flow

Postal code first. Five digits survive narrowband far better than place names.
Match the street. Against the official directory of that postal code, not against everything.
React to the status. confirmed read back · ambiguous read out choices · unresolved hand over.
Never guess. If the caller rejects everything: flag_for_human.

Hard cases

Runs live against this instance. Each row is a typical phone-line error – and what the server makes of it. Same cases as in the automated tests, but here against the real data of the postal code.

Postal code

Heard	Why it is hard	Status	Best match	Confidence

API

REST and MCP are equivalent – same business logic, same responses. Full description: /openapi.json · MCP tool describe_api · resource geocoder://docs/api

What the caller said

Conversation flow

Hard cases

API