Skip to main content
Glama

GBG Loqate - Reach

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
gbgplc/lqt
GitHub Stars
2
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 11 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: address retrieval, verification (single and batch), and policy management. The descriptions explicitly cross-reference each other (e.g., retrieve_address vs verify_address) to avoid confusion.

Naming Consistency4/5

Most tool names follow a verb_noun pattern (list_policies, retrieve_address, verify_address, verify_email, verify_phone), but show_policy and verify_contact deviate slightly: show_policy uses a different verb, and verify_contact covers multiple fields rather than a single noun. Still, the pattern is largely consistent and readable.

Tool Count5/5

With 11 tools, the set is well-scoped: it covers core verification operations (address, email, phone, contact) for both single and batch modes, plus policy management. No redundant tools, and each earns its place.

Completeness4/5

The surface covers verification and retrieval with both single and batch operations, and includes policy listing and detail. However, there is no tool to create, update, or delete policies (only list and show), which is a minor gap for policy management.

Available Tools

11 tools
list_policiesList PoliciesA
Read-only
Inspect

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

retrieve_addressRetrieve Address DetailsA
Read-only
Inspect

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.

Inputs: suggestion_id (required), key.

show_policyShow PolicyA
Read-only
Inspect

Show full details for a specific decisioning policy.

Inputs: name (required).

verify_addressVerify AddressA
Read-only
Inspect

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).

Inputs: id, key, policy, address, +49 more.

verify_address_batchVerify Addresses (Batch)A
Read-only
Inspect

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.

Inputs: addresses (required), key, policy, options, +3 more.

verify_contactVerify ContactA
Read-only
Inspect

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.

Inputs: id, key, email, phone, +51 more.

verify_contact_batchVerify Contacts (Batch)A
Read-only
Inspect

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.

Inputs: contacts (required), key, policy, options, +3 more.

verify_emailVerify EmailA
Read-only
Inspect

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.

Inputs: email (required), key, policy.

verify_email_batchVerify Emails (Batch)A
Read-only
Inspect

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.

Inputs: emails (required), key, policy.

verify_phoneVerify Phone NumberA
Read-only
Inspect

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.

Inputs: phone (required), key, policy, country.

verify_phone_batchVerify Phone Numbers (Batch)A
Read-only
Inspect

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.

Inputs: phones (required), key, policy.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables agents to validate and normalize phone numbers, email addresses, and postal addresses with production-grade, country-specific rules, including formatting, typo detection, and checks for disposable domains or fictional numbers.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to validate email addresses and phone numbers before saving or using them, including syntax, DNS/MX checks, disposable domains, role addresses, typo suggestions, and phone number formats. Supports bulk email validation for up to 50 addresses in a single call.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables sales and lead-generation agents to score emails and company domains, return keep/fix/review/drop actions, correct likely typos, and clean batch lead lists before outreach.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables agents to verify postal addresses, email addresses, and phone numbers against Melissa's Global Verification APIs before acting on the data, including batch verification and a per-session call budget to prevent runaway costs.
      4
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.