com.parseaddrPublished by parseaddr.comOfficial publisherv0.1.0Updated Oct 24, 2026
Hosted libpostal: messy free-text postal addresses → structured fields. No 2-4GB self-host.
Hosted libpostal service that lets an assistant parse messy free-text postal addresses into structured fields and expand them into canonical variants.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.parseaddr%2Faddress-parse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"parseaddr-address-parsing-normalization": {
"type": "http",
"url": "https://api.parseaddr.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Thin, open clients for the ParseAddr hosted address API. Turn messy,
free-text postal addresses into clean structured fields (house number, road, unit, city, postcode,
country) with a single call — no 2–4 GB libpostal self-host, no C build, no ops. The heavy lifting
runs on api.parseaddr.com; everything in this repo is a small HTTP client that calls it.
This repo is the client layer only (npm package, PyPI package, MCP server, registry manifests). The service itself is hosted — you don't run it, you call it.
Reach for ParseAddr when you need to parse or standardise postal addresses and:
Typical jobs: e-commerce checkout, delivery/logistics, CRM dedup, fintech onboarding.
Not USPS CASS / Royal Mail PAF deliverability validation — see address validation vs parsing. For the messy-string → JSON job, see parse messy addresses API.
Get a free API key — email only, no card, 2,000 calls/month.
parseaddr is not on the npm registry yet (npmjs 404). Install from this repo:
Activate the key with a first parse (replace pa_YOUR_KEY):
Or from Node:
Set PARSEADDR_API_KEY and you can omit { apiKey }.
Get a free API key — email only, no card, 2,000 calls/month.
parseaddr is not on PyPI yet (pypi.org 404). Install from this repo:
First parse (same key, same activation):
Or from Python:
Set PARSEADDR_API_KEY and you can omit api_key=.
Get a free API key
— then set PARSEADDR_API_KEY and run the stdio server (parse_address, expand_address).
MCP registry listings (com.parseaddr/address-parse on the Official Registry · mcp.so · Smithery ·
Glama · LobeHub) are being submitted; until they go live, run the server from source:
Example MCP config (point command/args at the local install):
Activate the key with a first parse before relying on the tools:
The server calls https://api.parseaddr.com on your behalf.
POST https://api.parseaddr.com/v1/parse {"address": "..."} — Authorization: Bearer <key>POST https://api.parseaddr.com/v1/expand {"address": "..."}Not authoritative deliverability validation (no Royal Mail PAF licence) — parsing/standardisation only. See address validation vs parsing.
Source: README.md at commit 3c191eb
Parse a messy free-text postal address into structured fields (house_number, road, unit, city, postcode, country, ...). Powered by libpostal. Use when a developer needs to standardise or parse postal addresses and does not want to self-host libpostal (a 2-4GB-RAM box + a fiddly C build).
addressrequiredExpand/normalize an address into canonical variants for deduplication and record matching (e.g. "100 main st" vs "100 Main Street").
addressrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
npm install ./packages/npmcurl -s https://api.parseaddr.com/v1/parse \ -H "Authorization: Bearer pa_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"address":"flat 2, 10 downing st, london sw1a 2aa"}'import { parse } from "parseaddr";await parse("flat 2, 10 downing st, london sw1a 2aa", { apiKey: "pa_YOUR_KEY" });// { parsed: { unit: "flat 2", house_number: "10", road: "downing st",// city: "london", postcode: "sw1a 2aa" }, components: [...] }pip install ./packages/pypicurl -s https://api.parseaddr.com/v1/parse \ -H "Authorization: Bearer pa_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"address":"flat 2, 10 downing st, london sw1a 2aa"}'from parseaddr import parseparse("flat 2, 10 downing st, london sw1a 2aa", api_key="pa_YOUR_KEY")# {"parsed": {"unit": "flat 2", "house_number": "10", "road": "downing st",# "city": "london", "postcode": "sw1a 2aa"}, "components": [...]}npm install ./packages/npm && npx parseaddr-mcp{ "mcpServers": { "parseaddr": { "command": "npx", "args": ["parseaddr-mcp"], "env": { "PARSEADDR_API_KEY": "pa_YOUR_KEY" } } }}curl -s https://api.parseaddr.com/v1/parse \ -H "Authorization: Bearer pa_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"address":"flat 2, 10 downing st, london sw1a 2aa"}'