mcpbeat

GBG Loqate - Reach MCP Server

io.github.gbgplc/lqt
answering

GBG Loqate - Reach is answering right now. Last checked 11 min ago. It exposes 7 tools. Last commit 30 Jul 2026.

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

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
219 ms
Response time
average over 24h
2
Stars
last commit 30 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add lqt --transport http https://reach.prod.fabric.gbgplatforms.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "lqt": {
      "url": "https://reach.prod.fabric.gbgplatforms.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.lqt]
url = "https://reach.prod.fabric.gbgplatforms.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "lqt": {
      "url": "https://reach.prod.fabric.gbgplatforms.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "lqt": {
      "url": "https://reach.prod.fabric.gbgplatforms.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
verify_address
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_contact
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_email
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_phone
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.
policies
list_policies
List available decisioning policies (strict, shipping, standard, permissive) with their thresholds.
retrieve
retrieve_address
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
show_policy
Show full details for a specific decisioning policy.

Endpoints

URLTransportStateLatencyChecked
https://reach.prod.fabric.gbgplatforms.com/mcp streamable-http answering 214 ms 11 min ago

GBG Loqate - Reach — questions

Answers built from our own checks of this server.

What can GBG Loqate - Reach do?
It exposes 7 tools, read directly from the server on our last check. Among them: list_policies, retrieve_address, show_policy, verify_address, verify_contact, verify_email and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is GBG Loqate - Reach working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 219 ms. The bar chart above shows every period we have measured.
How do I connect GBG Loqate - Reach?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does GBG Loqate - Reach need an API key?
No. GBG Loqate - Reach completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is GBG Loqate - Reach?
It answers our handshake in 219 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is GBG Loqate - Reach open source?
Yes — it is published under the NOASSERTION licence and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.