Resolve a street address to a Census tract
Question: Which tract contains a stated public address, and how strong is the match?
GEO MCP needs arranged access. Request access and confirm the supported geography, address volume and MCP client. This demonstration uses a public address, not customer location data. It does not use a public GEO endpoint.
1. Send one address
In the provisioned MCP client, call geo.resolve_address_to_tract with JSON arguments:
{"address": "1600 Pennsylvania Avenue NW, Washington, DC 20500"}
An authenticated read-only call on November 3, 2026 returned ok: true, match_quality: exact, and matched address 1600 PENNSYLVANIA AVE NW, WASHINGTON, DC, 20500. It reported tract GEOID 11001980000, county FIPS 11001, state FIPS 11, and no candidate list (candidates: null). The source chain named usaddress and census_structured. See the Census Geocoder method for the geographic reference.
2. Use the match at the right grain
An exact address-to-tract match identifies Census geography for this input. It does not establish parcel boundaries, property ownership, building identity or storm exposure. Record the original and normalized addresses, match quality and tract ID; confirm the source vintage before wider use.
This step contributes source geography and an entity-location relationship. It does not cite a property filing or check a financial claim.
If the address is ambiguous
- Review
match_qualityand any returned candidates. Do not silently choose a tract from a ZIP-code candidate list; one ZIP code can cross several tracts. - Clarify incomplete or unmatched addresses before relying on the geography. An empty response is a coverage limit, not proof that the place does not exist.
- Ask about current source vintage and configured operations before applying the method to another geography. Storm screening and experimental parcel composition were not verified by this example.
For coverage and setup terms, see GEO MCP. To find geographic datasets after resolving the place, see Reveal MCP.