MCP server for DeepL translation API
Nothing to run from here
GBG Loqate - Reach is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Verify addresses, email addresses, and phone numbers with confidence scores.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http gbg-loqate-reach-mcp https://reach.prod.fabric.gbgplatforms.com/mcp
# 2 — ask your agent for something these tools do
# list_policies, retrieve_address, show_policy and 8 more
GBG Loqate - Reach costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GBAll 1 server
gbgplc1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http gbg-loqate-reach-mcp https://reach.prod.fabric.gbgplatforms.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List available decisioning policies (strict, shipping, standard, permissive) with their thresholds.
No parameter schema on file.
Resolve a suggestion id from address.suggestions into its full cleansed address components (organisation, sub-building, number, street, city, province, postcode, country). Use this when you need the address itself — to fill a form or show a confirmation — rather than a decision; to verify a chosen suggestion instead, pass 'suggestion_id' to verify_address. CONSUMES A LOQATE CREDIT per call, so res
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| suggestion_id | string | yes | Id of a suggestion previously returned in address.suggestions. CONSUMES A LOQATE CREDIT. Ids are not stable over time; a stale one returns SUGGESTION_NOT_FOUND and you must search again rather than re |
Show full details for a specific decisioning policy.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Policy name: strict shipping standard or permissive |
Verify an address against Loqate's global reference data. Returns a confidence score (0-1), verification status, and a policy-driven accept/review/reject recommendation. Set 'suggest' to also get alternative addresses suggested by Loqate whenever the address does not clear the policy; offer them to the user and verify the chosen one in a second call before treating it as good. Suggestions require
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header (get one at account.loqate.com) |
| verify_url | string | no | Custom address verification endpoint URL (overrides LOQATE_VERIFY_URL env var) |
| verify_key | string | no | Custom address verification API key (overrides LOQATE_VERIFY_KEY env var) |
| address | string | no | Full address string (free-form — use this OR structured fields below) |
| suggestion_id | string | no | Id of a suggestion previously returned in address.suggestions. The tool retrieves that address's cleansed components from Loqate and verifies those, which is how you confirm a suggestion the user chos |
| locality | string | no | City or town |
| admin_area | string | no | State or province |
| postcode | string | no | Postal or ZIP code |
| country | string | no | ISO 2-letter country code (e.g. US GB DE) |
| detect_country | boolean | no | When true and no country is supplied, guess the country from the address and flag the guess in the result (country_guessed). Address-only; off by default |
| suggest | boolean | no | When true, look up alternative addresses suggested by Loqate and return them in the result as suggestions. Requires the Loqate address-suggestion feature to be enabled on the account (licensed separat |
| suggest_limit | integer | no | Maximum number of suggestions to return (1-10, default 5). Requires suggest |
| suggest_below | null/number | no | Confidence floor for suggestions (0-1). An accepted address scoring below it still gets suggestions — policies accept from their own minimum, so an accepted address is not necessarily a confident one. |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
| options | object | no | Loqate API options as nested JSON, e.g. {"ServerOptions": {"FieldStatus": "true"}}. Dot notation is equivalent: {"ServerOptions.FieldStatus": "true"}. Pass GeoCode here as a boolean — it is sent at th |
| address2 | string | no | Second address line |
| address3 | string | no | Third address line |
| address4 | string | no | Fourth address line |
| address5 | string | no | Fifth address line |
| address6 | string | no | Sixth address line |
Verify up to 100 addresses in one call. Up to 100 records per call; the results array is in submission order and each entry carries its input index, so results can be zipped back onto rows without relying on order. One bad record fails only itself — it carries an error while the rest are verified. Suggestions are not available in batch. Records are grouped by country before being sent, as Loqate r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| verify_url | string | no | Custom address verification endpoint URL |
| verify_key | string | no | Custom address verification API key |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
| options | object | no | Loqate API options as nested JSON, applied to every record in the batch |
| detect_country | boolean | no | When true, guess the country of any record that does not supply one, from its address text, and flag the guess in that record's result. Records are then grouped by their detected country, so a mixed-c |
| addresses | null/array | yes | Addresses to verify, up to 100. Results are returned in the same order, each carrying its input index |
Verify address, email, and/or phone together. Returns individual results plus an overall recommendation (most conservative of all provided fields). Set 'suggest' to also get alternative addresses suggested by Loqate whenever the address does not clear the policy; offer them to the user and verify the chosen one in a second call before treating it as good. Suggestions require a separately licensed
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| verify_url | string | no | Custom address verification endpoint URL (overrides LOQATE_VERIFY_URL env var) |
| verify_key | string | no | Custom address verification API key (overrides LOQATE_VERIFY_KEY env var) |
| address | string | no | Full address string |
| suggestion_id | string | no | Id of a suggestion previously returned in address.suggestions. The tool retrieves that address's cleansed components from Loqate and verifies those, which is how you confirm a suggestion the user chos |
| locality | string | no | City or town |
| admin_area | string | no | State or province |
| postcode | string | no | Postal or ZIP code |
| country | string | no | ISO 2-letter country code |
| detect_country | boolean | no | When true and no country is supplied, guess the country from the address and flag the guess in the result (country_guessed). Address-only — does not affect phone or email; off by default |
| suggest | boolean | no | When true, look up alternative addresses suggested by Loqate and return them under address.suggestions. Requires the Loqate address-suggestion feature to be enabled on the account (licensed separately |
| suggest_limit | integer | no | Maximum number of suggestions to return (1-10, default 5). Requires suggest |
| suggest_below | null/number | no | Confidence floor for suggestions (0-1). An accepted address scoring below it still gets suggestions. Omit to use the policy value (standard 0.85); 0 disables the floor. Address-only |
| string | no | Email address to verify | |
| phone | string | no | Phone number to verify |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
| options | object | no | Loqate API options as nested JSON, e.g. {"ServerOptions": {"FieldStatus": "true"}}. Dot notation is equivalent: {"ServerOptions.FieldStatus": "true"}. Pass GeoCode here as a boolean — it is sent at th |
| address2 | string | no | Second address line |
| address3 | string | no | Third address line |
| address4 | string | no | Fourth address line |
Verify up to 100 contacts in one call, each with any combination of address, email and phone, returning an overall recommendation per contact. Results are in submission order and each carries its input index. One bad record fails only itself, and a field that cannot be verified does not remove the contact — the overall recommendation is drawn from whichever fields were checked. The three types run
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| verify_url | string | no | Custom address verification endpoint URL |
| verify_key | string | no | Custom address verification API key |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
| options | object | no | Loqate API options as nested JSON, applied to every address in the batch |
| detect_country | boolean | no | When true, guess the country of any contact whose address does not supply one and flag the guess in that contact's address result. Off by default |
| contacts | null/array | yes | Contacts to verify, up to 100. Results are returned in the same order, each carrying its input index |
Verify an email address via Loqate. Returns confidence, risk level, and accept/review/reject recommendation. Requires a Loqate API key — pass it via the 'key' field.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| string | yes | Email address to verify | |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
Verify up to 100 email addresses in one call. Up to 100 records per call; the results array is in submission order and each entry carries its input index, so results can be zipped back onto rows without relying on order. One bad record fails only itself — it carries an error while the rest are verified. Suggestions are not available in batch. The batch endpoint returns less detail than single veri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
| emails | null/array | yes | Email addresses to verify, up to 100. Results are returned in the same order, each carrying its input index |
Verify a phone number via Loqate. Returns confidence, number type, carrier, and accept/review/reject recommendation. Requires a Loqate API key — pass it via the 'key' field.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| phone | string | yes | Phone number (E.164 format preferred e.g. +442071234567) |
| country | string | no | ISO 2-letter country code (helps with parsing if no country prefix) |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
Verify up to 100 phone numbers in one call. Up to 100 records per call; the results array is in submission order and each entry carries its input index, so results can be zipped back onto rows without relying on order. One bad record fails only itself — it carries an error while the rest are verified. Suggestions are not available in batch. Phone validation has no bulk endpoint, so numbers are che
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | no | Loqate API key — required unless the server has one configured or the request carries an Authorization: Bearer header |
| policy | string | no | Policy name: strict shipping standard (default) or permissive |
| phones | null/array | yes | Phone numbers to verify, up to 100. Results are returned in the same order, each carrying its input index |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GBG Loqate - Reach or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.6.2.
0.6.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish GBG Loqate - Reach can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.