address-validator
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@address-validatorvalidate this address: 123 Main St, New York, NY 10001"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Address Validator API
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.):
{
"mcpServers": {
"address-validator": {
"url": "https://address-validator.api.klymax402.com/mcp"
}
}
}Related MCP server: Postio
Quickstart -- HTTP (x402)
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 bodyAny x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
Tools
Tool | Method | Path | Price | Description |
| POST |
| $0.008 | Parse, 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
Name | Type | Required | Description |
| string | yes | Full address string to parse and validate (e.g. '123 Main St, New York, NY 10001') |
Example response:
{"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.
Catalog: https://klymax402.com/llms.txt
Full API reference: https://klymax402.com/llms-full.txt
Live stats: https://klymax402.com/stats
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Br0ski777/address-validator-x402'
If you have feedback or need assistance with the MCP directory API, please join our Discord server