Verify addresses, email addresses, and phone numbers with confidence scores.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Verify addresses, emails, and phone numbers against Loqate's APIs.
Get confidence scores, policy-aware recommendations, and full auditability β in one command.
Real-time verification decisioning for agents that need to know whether contact data is good enough for the job.
Part of GBG Reach.
lqt verify Β Β·Β lqt parse Β Β·Β lqt mcp
lqt_windows_amd64.zip from the latest releaselqt.exePATH, or run it directlySee Releases for all versions and platforms. Each release includes SHA-256 checksums.
| Platform | Archive |
|---|---|
| macOS (Apple Silicon) | lqt_*_darwin_arm64.tar.gz |
| macOS (Intel) | lqt_*_darwin_amd64.tar.gz |
| Linux (x86_64) | lqt_*_linux_amd64.tar.gz |
| Linux (ARM64) | lqt_*_linux_arm64.tar.gz |
| Windows (x86_64) | lqt_*_windows_amd64.zip |
You need a Loqate API key for verification. Optionally, an Anthropic API key for the parse command.
macOS / Linux:
Windows (PowerShell):
macOS / Linux:
Windows (PowerShell):
Verify addresses, emails, and/or phone numbers against Loqate's APIs. Returns a confidence score and a policy-driven recommendation (accept, review, or reject).
Flags:
| Flag | Short | Description |
|---|---|---|
--address | -a | Full address to verify |
--locality | City/town | |
--admin-area | State/province | |
--postcode | Postal/ZIP code | |
--country | -c | ISO 2-letter country code |
--detect-country | When no country is supplied, guess it from the address and flag the guess in the result. Address-only; off by default. | |
--suggest | When the address does not clear the policy (review or reject), look up alternative addresses suggested by Loqate and return them under address.suggestions. Not called for an accepted address. Requires a separately licensed Loqate feature enabled on your account. Address-only; off by default; not available with --batch. | |
--suggest-limit | Maximum suggestions to return, 1β10 (default 5). Requires --suggest. | |
--suggest-below | Confidence floor for suggestions: an accepted address scoring below it still gets suggestions. Defaults to the active policy's value (standard 0.85). 0 disables the floor. Requires --suggest. | |
--suggestion-id | Verify a suggestion the user chose, by its id from address.suggestions. Resolves the id to its cleansed components and verifies those. Use instead of --address. Consumes a Loqate credit. Not available with --batch or --dry-run. | |
--email | -e | Email address to verify |
--phone | -p | Phone number (E.164 format) |
--key | -k | Loqate API key (overrides env) |
--policy | Policy name: strict, shipping, standard, permissive | |
--policy-file | Path to custom policy JSON file | |
--batch | -b | CSV/TSV/pipe-delimited file path (or - for stdin) |
--delimiter | -d | Batch delimiter: comma, tab, pipe (auto-detected if omitted) |
--output | -o | Output format: json, jsonl, table |
--summary | -s | Show batch summary statistics |
--field | Extra Loqate input field Key=Value (repeatable) | |
--option | Loqate API option Key=Value (repeatable, dot notation for nesting) | |
--jsonl | JSON Lines output (one object per line) | |
--no-color | Disable color output | |
--verify-url | Custom address verification endpoint URL (overrides LOQATE_VERIFY_URL env var) | |
--verify-key | Custom address verification API key (overrides LOQATE_VERIFY_KEY env var). When set, --key is not required for address-only verification. | |
--verbose | -v | Show reasoning log |
Examples:
Full list of input fields and API options: Loqate International Batch Cleanse API
--suggest)Licensing. Suggestions use a Loqate feature that is licensed separately from address verification and must be enabled on your account. If it isn't, nothing breaks: the verification still returns its normal result and exit code, and the reason appears in
suggestions.error(typically an unknown-key or licence message from Loqate). Talk to your Loqate account contact to have it enabled.
Verification tells you an address is wrong. Suggestions tell you what the right one probably
is. Add --suggest and lqt asks Loqate for real addresses matching what was typed, returning
them with the decision.
The lookup runs when either:
review or reject), orstandard β see the Policies table).The second case is the one that catches near-misses. A policy accepts anything at or above its
minimum confidence, so accepted is not the same as confident: on standard the input
marsh wall, E14 9TN matches a street and scores exactly 0.55, which is accepted β yet the
house number is missing and better addresses exist. Use --suggest-below to move that line
(--suggest-below 0 turns the confidence check off and only suggests on review/reject).
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/gbg-loqate-reach)<a href="https://allmcps.com/mcp/gbg-loqate-reach"><img src="https://allmcps.com/api/badge/gbg-loqate-reach?style=directory" alt="GBG Loqate Reach on AllMCPs" /></a>