Mmcp.market

GBG Loqate - Reach MCP server

online · 100% uptime
by gbgplc·io.github.gbgplc/lqt·v0.6.2·2 stars
No reviews yet

Verify addresses, email addresses, and phone numbers with confidence scores.

B83/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed GBG Loqate - Reach yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

GBG Loqate - Reach tools (11, 2 write)

write = sends, deletes, buys or posts
  • list_policiesFree

    List available decisioning policies (strict, shipping, standard, permissive) with their thresholds.

  • retrieve_addressFree

    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 resolve only the one suggestion the user chose. The result is reference data, NOT a verification. Requires a Loqate API key.

  • show_policyFree

    Show full details for a specific decisioning policy.

  • verify_addressFree

    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 a separately licensed Loqate feature enabled on the account — without it, verification still succeeds and the problem is reported in suggestions.error. Requires a Loqate API key — pass it via the 'key' field (get one at account.loqate.com).

  • verify_address_batchFree

    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 recommends, so the cost is one upstream call per distinct country in the batch rather than one per call. Set detect_country to guess the country of records that do not supply one — detection runs per record, before grouping, so a mixed batch still sends each group with the right default. Requires a Loqate API key — pass it via the 'key' field.

  • verify_contactFree

    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 Loqate feature enabled on the account — without it, verification still succeeds and the problem is reported in suggestions.error. Requires a Loqate API key — pass it via the 'key' field.

  • verify_contact_batchFree

    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 concurrently, so a full batch is paced by email at roughly 7 seconds per 100. Requires a Loqate API key — pass it via the 'key' field.

  • verify_emailwrite actionFree

    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.

  • verify_email_batchwrite actionFree

    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 verification: risk, complainer and reason are absent, though the accept/review/reject recommendation and the disposable-mailbox flag are identical. Requires a Loqate API key — pass it via the 'key' field.

  • verify_phoneFree

    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.

  • verify_phone_batchFree

    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 checked concurrently against a shared limit. Measured at around 2.6s for 100 numbers, which is the fastest of the three batch types — email is the slowest, at roughly 7s for 100, because it probes mail servers. Requires a Loqate API key — pass it via the 'key' field.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 992ms20/20
  • Tool poisoning11 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenancelast push 14 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install GBG Loqate - Reach in Claude Code, Cursor or VS Code

claude mcp add --transport http lqt https://reach.prod.fabric.gbgplatforms.com/mcp
Add to Cursor

What the publisher says

From the GBG Loqate - Reach repository's README, as published. We do not edit it. Read it on GitHub

Loqate CLI

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

Install

macOS

# Apple Silicon (M1/M2/M3/M4)
curl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_darwin_arm64.tar.gz | tar xz
sudo mv lqt /usr/local/bin/

# Intel
curl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_darwin_amd64.tar.gz | tar xz
sudo mv lqt /usr/local/bin/

Linux

# x86_64
curl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_linux_amd64.tar.gz | tar xz
sudo mv lqt /usr/local/bin/

# ARM64
curl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_linux_arm64.tar.gz | tar xz
sudo mv lqt /usr/local/bin/

Windows

  1. Download lqtwindowsamd64.zip from the latest release
  2. Extract lqt.exe
  3. Move it to a directory on your PATH, or run it directly

Verify Installation

lqt version

All Downloads

See Releases for all versions and platforms. Each release includes SHA-256 checksums.

Quick Start

API Keys

You need a Loqate API key for verification. Optionally, an Anthropic API key for the parse command.

macOS / Linux:

export LOQATE_API_KEY=your-key-here

# Optional — for lqt parse
export ANTHROPIC_API_KEY=your-key-here

Windows (PowerShell):

$env:LOQATE_API_KEY="your-key-here"

# Optional — for lqt parse
$env:ANTHROPIC_API_KEY="your-key-here"

Your First Verification

macOS / Linux:

# Verify an address
lqt verify --address "125 Summer Street, Boston, MA 02110, US"

# Verify address + email + phone with a policy
lqt verify -a "10 Downing St, London, GB" \
           -e "pm@gov.uk" \
           -p "+442071234567" \
           --policy shipping

# Parse and standardize without calling Loqate (uses Claude)
lqt parse --address "125 summer street boston ma 02110 us"

Windows (PowerShell):

# Verify an address
.\lqt.exe verify --address "125 Summer Street, Boston, MA 02110, US"

# Verify address + email + phone with a policy
.\lqt.exe verify -a "10 Downing St, London, GB" -e "pm@gov.uk" -p "+442071234567" --policy shipping

# Parse and standardize without calling Loqate (uses Claude)
.\lqt.exe parse --address "125 summer street boston ma 02110 us"

Commands

verify

Verify addresses, emails, and/or phone numbers against Loqate's APIs. Returns a confidence score and a policy-driven recommendation (accept, review, or reject).

lqt verify [flags]

Flags:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

GBG Loqate - Reach: common questions

Is GBG Loqate - Reach MCP server safe?
Mostly: it is graded B (83/100). Read the GBG Loqate - Reach safety report
How do I install GBG Loqate - Reach?
It runs remotely at reach.prod.fabric.gbgplatforms.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does GBG Loqate - Reach need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is GBG Loqate - Reach maintained?
The last commit was 14 days ago (2026-09-14). The latest release is v0.6.2.
Is GBG Loqate - Reach up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of GBG Loqate - Reach?
Servers from other publishers that do the same job: Agent Identity MCP server, ContrastAPI MCP server and Hail MCP server. Compare all GBG Loqate - Reach alternatives.

Alternatives to GBG Loqate - Reach

Same job from other publishers: the closest match first, then the best rated.

All GBG Loqate - Reach alternatives →
  • Agent Identity
    Gives an AI agent a disposable email and a real UK phone number to test signup flows.
    B
  • ContrastAPI
    55 tools, 7 Resources, Sigma rules, email SPF/DMARC, MITRE, CVE/KEV, risk_score. No key.
    B
  • Hail
    Phone, SMS & email for AI agents — one remote MCP endpoint, OAuth login, zero install.
    B
  • EmptyInbox
    Zero-config disposable email inboxes for AI agents: create, read mail, await verify codes.
    B
  • ParseAPI
    Official ParseAPI MCP. Place, IP, email, phone, weather, currency lookups.
    A

More from gbgplc →