MartechDB
MartechDB
Toggle sidebar

Loqate MCP server

loqate.com, agents.gbg.com

Yes. Loqate publishes an official MCP server at https://reach.prod.fabric.gbgplatforms.com/mcp. It's hosted. It offers 11 tools. We last checked it on 22 Nov 2026.

Official MCP server
Hosted
Sign-in: see vendor docs

Official: published in the official MCP Registry as io.github.gbgplc/lqt, from the gbgplc GitHub account. Checked 22 Nov 2026. Maintained by Stuart Brameld.

Key facts

As of 22 Nov 2026, Loqate's official MCP server scores 65/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 55 of our 55 checks in the last 90 days and lists 11 tools.

How the Agent Readiness Index works · Wrong? Suggest a correction

Loqate MCP server review

65/100

Loqate's GBG Loqate - Reach scores 65/100 on MartechDB's Agent Readiness Index: easy to connect an AI agent to, with a few gaps.

The good

  • Hosted by Loqate: connect by URL, with nothing to install

  • Documented, with 11 tools known

  • Published to the official MCP Registry

  • Answered 100% of our checks in the last 90 days

The bad

  • Nothing we've found.

Not checked yet: how you sign in. Anything not checked scores nothing.

Official MCP server

GBG Loqate - Reach

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

Address
https://reach.prod.fabric.gbgplatforms.com/mcp
Runs
Hosted
Sign-in
Sign-in: see vendor docs
Vendor docs
Cost to use
Metered
Plan: Existing Loqate account and API key
Loqate credits per lookup; per-IP rate limiting; batch tools capped at 100 records per call
Official MCP Registry
Listed as io.github.gbgplc/lqt · published 7 May 2026
How we know it's official
  • Published in the official MCP Registry as io.github.gbgplc/lqt, from the gbgplc GitHub account.
Checked 22 Nov 2026.
Documentation
agents.gbg.com/reach
Source code
github.com/gbgplc/lqt
Tools
11 tools · listed 22 Nov 2026
First seen
7 May 2026
Last checked
Reachable ·
16 Nov 2026: reachable
17 Nov 2026: reachable
18 Nov 2026: reachable
19 Nov 2026: reachable
20 Nov 2026: reachable
21 Nov 2026: reachable
22 Nov 2026: reachable
Uptime
100% · 55 of 55 checks reachable since 1 Oct 2026

GBG Loqate - Reach tools (11)

As the server lists them. Names and descriptions are the vendor's own.

  • list_policies List Policies
    Read-only

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

  • retrieve_address Retrieve Address Details
    Read-only

    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_policy Show Policy
    Read-only

    Show full details for a specific decisioning policy.

  • verify_address Verify Address
    Read-only

    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_batch Verify Addresses (Batch)
    Read-only

    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_contact Verify Contact
    Read-only

    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_batch Verify Contacts (Batch)
    Read-only

    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_email Verify Email
    Read-only

    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_batch Verify Emails (Batch)
    Read-only

    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_phone Verify Phone Number
    Read-only

    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_batch Verify Phone Numbers (Batch)
    Read-only

    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.

Connect your AI to Loqate

Add the official Loqate MCP server to Claude, ChatGPT or your editor.

Connect Loqate MCP to Claude

Claude.ai and Claude Desktop

  1. Open Customize, then Connectors.

  2. Click +, then Add custom connector.

  3. Name it Loqate, paste the address below and click Add.

Claude Code

Loqate MCP server questions

Does Loqate have an official MCP server?

Yes. Loqate publishes its MCP server itself. It's in the official MCP Registry, published under Loqate's name. MartechDB only lists servers a vendor publishes, never community copies.

What is the Loqate MCP server URL?

The address is https://reach.prod.fabric.gbgplatforms.com/mcp.

How do I connect Loqate MCP to Claude, ChatGPT or Cursor?

In Claude, add https://reach.prod.fabric.gbgplatforms.com/mcp as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http loqate https://reach.prod.fabric.gbgplatforms.com/mcp

What can the Loqate MCP server do?

It offers 11 tools, including list_policies, retrieve_address, show_policy, verify_address and verify_address_batch (as listed on 22 Nov 2026). All of them are marked read-only.

Is the Loqate MCP server in the official MCP Registry?

Yes, as io.github.gbgplc/lqt.

Is the Loqate MCP server working?

Yes. It answered our most recent check. We last checked it on 22 Nov 2026.

What are the alternatives to Loqate's MCP server?

In Customer data, the most agent-friendly alternatives with an official MCP server are ChatGPT in Google Sheets (100/100), Octoparse (94/100), MrScraper (91/100), Sparktoro (88/100) and Attensira (88/100). Loqate scores 65/100 on the same index.

Alternatives to Loqate's MCP server

Vendors in Customer data with an official MCP server, the most agent-friendly first. Loqate scores 65/100.

Compare all 46 Customer data vendors →

Use with AI

Connect your AI to MartechDB

Then ask it about Loqate, or any of the 1,850 marketing tools with an official MCP server. Free, no sign-in.

Claude.ai and Claude Desktop

  1. Open Customize, then Connectors.

  2. Click +, then Add custom connector.

  3. Name it MartechDB, paste the address below and click Add. There's no sign-in.

The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.

Show that your MCP server is verified

If you work at Loqate, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.

Official MCP server, verified by MartechDB
HTML
Markdown

Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.