Connect-MCP

GBG Loqate - Reach

io.github.gbgplc/lqt · v0.6.2

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

MCPremoteno credentialsE-commerceEmail

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 11 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 100/100

What it does: 11 tools · 11 read, 0 write · Email, E-commerce

Test call list_policies: worked (856 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://reach.prod.fabric.gbgplatforms.com/mcp

Tools

11 tools listed at last check
  • list_policies List available decisioning policies (strict, shipping, standard, permissive) with their thresholds.
  • 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 s
  • show_policy Show full details for a specific decisioning policy.
  • 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
  • verify_address_batch 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. S
  • 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 th
  • verify_contact_batch 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 c
  • 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_email_batch 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 verif
  • 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.
  • verify_phone_batch 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 verifie

Badge

Connect-MCP badge for io.github.gbgplc/lqt

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.gbgplc/lqt.svg)](https://clawy.uk/mcp/s/io.github.gbgplc/lqt)

Repository · Website