Address Validator API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

Parse, validate and normalize postal addresses. Detect country, verify format. x402.

VerifiedSSEWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant parse, validate and normalize postal addresses for the US, UK, France and Germany, paid per call.

What you can do
Parse, validate and normalize a full postal address string into structured components (street, city, state, postal code, country). Detect the country and check whether the postal code format is valid. Return a normalized address, a validity flag and a confidence score as JSON.
When to use it
Useful when cleaning CRM records, checking e-commerce checkout or shipping addresses, normalizing address data, or doing basic KYC address verification for US, UK, French or German addresses. Not intended for phone, email or PII checks.
Requirements
A remote MCP client that can connect to the hosted endpoint over SSE; no API key or signup. Each call is paid in USDC on Base L2 through the x402 protocol, so an x402-aware client with a funded wallet is needed to complete the payment challenge.
Before you install
Every call costs money (listed at $0.008 per validation) and is settled in USDC on Base, so a wallet and spending are involved. Addresses you submit are sent to a third-party service. Payment is handled by Coinbase CDP and PayAI facilitators.

Installation

In SourceWeft

  1. Open Address Validator API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

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/io.github.Br0ski777%2Faddress-validator/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "address-validator-api": {
      "type": "sse",
      "url": "https://address-validator.api.klymax402.com/mcp"
    }
  }
}

README

Address Validator API

[MCP Server] [x402] [License: MIT]

Parse and validate postal addresses -- country detection, component split, postal code verification. US/UK/FR/DE. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "address-validator": {      "url": "https://address-validator.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl -X POST "https://address-validator.api.klymax402.com/api/validate" \  -H "Content-Type: application/json" \  -d '{"address":"0x0000000000000000000000000000000000dEaD"}'# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
address_validatePOST/api/validate$0.008Parse, validate, and normalize a postal address

address_validate

Use this when you need to parse, validate, or normalize a postal address. Returns structured address components in JSON.

Parameters

NameTypeRequiredDescription
addressstringyesFull address string to parse and validate (e.g. '123 Main St, New York, NY 10001')

Example response:

json
{"address":"123 Main St, New York, NY 10001","valid":true,"components":{"street":"123 Main St","city":"New York","state":"NY","postalCode":"10001","country":"United States"},"normalizedAddress":"123 Main St, New York, NY 10001, US","detectedCountry":"United States","postalCodeValid":true,"confidence":0.95}

When to use: CRM data cleaning, e-commerce checkout validation, shipping address normalization, and KYC address verification.

Not for: phone validation (use phone_validate_number), email validation (use email_verify_address), PII detection in text (use compliance_detect_pii).

Example agent prompts

  • "Parse, validate, or normalize a postal address"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit 0c3a957

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% 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.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts