# ParseAddr — Address Parsing & Normalization (remote · api.parseaddr.com)

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

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.parseaddr.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-parseaddr-address-parse/api.md), [page](https://verifymcp.io/servers/com-parseaddr-address-parse/api)

## Channel facts

- Endpoint: `https://api.parseaddr.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 218 tokens (~109/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ParseAddr — Address Parsing & Normalization MCP server?

ParseAddr — Address Parsing & Normalization is a hosted endpoint at https://api.parseaddr.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-parseaddr-address-parse": {
      "type": "remote",
      "url": "https://api.parseaddr.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-parseaddr-address-parse --url 'https://api.parseaddr.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-parseaddr-address-parse:
    url: "https://api.parseaddr.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-parseaddr-address-parse": {
      "Transport": "http",
      "Url": "https://api.parseaddr.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-parseaddr-address-parse -t streamable-http -u 'https://api.parseaddr.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-14 (score 77, +1)

- [security] Stability: 0.97 → pass

### 2026-11-12 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 75, +52)

- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: fail → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.87

### 2026-11-09 (score 23, −51)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.80 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-07 (score 74, +1)

- [functional improvement] Endpoint reachability: unreachable → reachable

### 2026-11-06 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 72, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.63 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `parse_address` (~90 tokens)

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

Input parameters:

- `address` (string, required)

### `expand_address` (~48 tokens)

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

Input parameters:

- `address` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-parseaddr-address-parse/api#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75
- 2026-11-09: 23
- 2026-11-08: 74
- 2026-11-07: 74
- 2026-11-06: 73
- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 67

## Common questions

### What is the ParseAddr — Address Parsing & Normalization MCP server?

ParseAddr — Address Parsing & Normalization is an MCP server listed in the public MCP registry as com.parseaddr/address-parse. Hosted libpostal: messy free-text postal addresses → structured fields. No 2-4GB self-host. This page covers its hosted endpoint (https://api.parseaddr.com/mcp).

### Is the ParseAddr — Address Parsing & Normalization MCP server safe to use?

ParseAddr — Address Parsing & Normalization scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ParseAddr — Address Parsing & Normalization MCP server expose?

ParseAddr — Address Parsing & Normalization exposes 2 tools: parse_address, expand_address. Their descriptions and schemas cost roughly 138 tokens of context every time the server is loaded.

### Does the ParseAddr — Address Parsing & Normalization MCP server require authentication?

No. We connected to ParseAddr — Address Parsing & Normalization without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ParseAddr — Address Parsing & Normalization MCP server still maintained?

ParseAddr — Address Parsing & Normalization is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ParseAddr — Address Parsing & Normalization MCP server?

VerifyMCP ran 12 checks on ParseAddr — Address Parsing & Normalization, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ParseAddr — Address Parsing & Normalization: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.parseaddr.com/mcp
- Authorisation metadata: https://api.parseaddr.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/wezpyke/parseaddr-mcp
- Website: https://parseaddr.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-parseaddr-address-parse/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-parseaddr-address-parse/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-parseaddr-address-parse/api.json
- HTML version of this page: https://verifymcp.io/servers/com-parseaddr-address-parse/api
