ParseAddr — Address Parsing & Normalization MCP Server

by parseaddr Your server? Claim it

answering

ParseAddr — Address Parsing & Normalization is answering right now. Last checked 3 min ago. It exposes 2 tools. Last commit 20 Sep 2026.

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

Uptime history 22 days of history · worst day 0%

22 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

231 ms

Response time

average over 24h

Stars

last commit 20 Sep 2026

Nothing serious here today

Today is the operative word: we check ParseAddr — Address Parsing & Normalization every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add address-parse --transport http https://api.parseaddr.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.parseaddr.com/mcp

~/.codex/config.toml

[mcp_servers.address-parse]
url = "https://api.parseaddr.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "address-parse": {
      "url": "https://api.parseaddr.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "address-parse": {
      "type": "http",
      "url": "https://api.parseaddr.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

expand

expand_address

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

parse

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 C build).

Endpoints

URL	Transport	State	Latency	Checked
https://api.parseaddr.com/mcp	streamable-http	answering	225 ms	3 min ago

Alternatives to ParseAddr — Address Parsing & Normalization

same job, measured the same way

Jp Address

by streamfront

Normalize and verify Japanese postal addresses into structured fields for agents.

1 tools answering

Ground Motion

by sibfly

Measured ground motion per US address (NASA InSAR). Self-register, $0.40/report, misses free.

9 tools answering

Advanced Excel

by antonio-castellon

Normalize messy lab Excel and CSV exports into structured tables.

112 installs/wk local only

Streamparse

by mukundakatta

Parse partial / truncated / messy JSON for LLM tool calls and structured outputs.

37 installs/wk local only

Umbryn MCP

by rinava

Redacts PII/PHI from text before it reaches an LLM. Fail-closed, self-hosted, no egress.

87 installs/wk local only

Excel Semantic Normalizer

by climik

Normalizes messy Excel spreadsheets into canonical JSON, mapping any headers to 19 standard fields.

local only

Agentcast

by mukundakatta

Structured-output enforcer: extract and validate JSON from messy LLM text.

38 installs/wk local only

Fuel Prices

by johnisanerd

Gas and fuel prices by station and area, as structured data via a hosted MCP server.

answering

ParseAddr — Address Parsing & Normalization — questions

Answers built from our own checks of this server.

What can ParseAddr — Address Parsing & Normalization do?

It exposes 2 tools, read directly from the server on our last check. Among them: expand_address, parse_address. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is ParseAddr — Address Parsing & Normalization working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 231 ms. The bar chart above shows every period we have measured.

How do I connect ParseAddr — Address Parsing & Normalization?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does ParseAddr — Address Parsing & Normalization need an API key?

No. ParseAddr — Address Parsing & Normalization completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is ParseAddr — Address Parsing & Normalization?

It answers our handshake in 231 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is ParseAddr — Address Parsing & Normalization open source?

The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.parseaddr.com, which runs on its operator's own terms.