NestDaddy

ParseAddr — Address Parsing & Normalization

com.parseaddr/address-parse · v0.1.0

Hosted libpostal: messy free-text postal addresses → structured fields. No 2-4GB self-host.

Connect Remote server

Terminal
claude mcp add --transport http address-parse https://api.parseaddr.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
~/.cursor/mcp.json
{
  "mcpServers": {
    "address-parse": {
      "url": "https://api.parseaddr.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "address-parse": {
      "type": "http",
      "url": "https://api.parseaddr.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://api.parseaddr.com/mcp

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools 2 found in our last check

  • parse_address

    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…

  • expand_address

    Expand/normalize an address into canonical variants for deduplication and record matching (e.g. "100 main st" vs "100 Main Street").

Headers

NameDescription
Authorization
Required, secret
Bearer ParseAddr API key from https://parseaddr.com

Details

Endpointhttps://api.parseaddr.com/mcp (Streamable HTTP)
First published12 Oct 2026
Last updated12 Oct 2026
Registry namecom.parseaddr/address-parse

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.