How do I connect an AI agent to Limitguard Lead Verification?

Use the MCP streamable HTTP endpoint https://api.limitguard.ai/mcp.

Catalog › ai.limitguard.api/limitguard

Is Limitguard Lead Verification reliable?

Flaky Partly. Faceabot measured Limitguard Lead Verification 27 times and only 96% of checks succeeded. Plan a fallback. It also does the job: its real read-only task worked 26 of 26 times.

Last check: 2026-10-19 16:50 UTC · answered in 8000 ms · remote (no install)

En français : Instable. Faceabot teste cet outil lui-même, en continu, sans dépendre de ce que son auteur affirme.

What it does

Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources.

Source: official MCP registry (registry.modelcontextprotocol.io) · version 2.11.9 · publisher website

Connect your agent

{
  "mcpServers": {
    "limitguard": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}

Or ask Faceabot first: MCP tool check_reliability {"id":"ai.limitguard.api/limitguard"} on https://faceabot.com/api/mcp.

Does it actually do the job?

Does the job (tested) — Faceabot asked verify_lead to do a small read-only task 26 time(s): 26 returned a real result, the last 26 in a row. Last result: ok in 1784 ms.

Sample input: {"country":"US"}. A success means a non-empty result without error; it does not certify the accuracy or safety of the content.

Faceabot measurements

When	Answers	Real task	Latency
2026-10-19 16:50 UTC	❌ timeout		8000 ms
2026-10-19 02:20 UTC	✅ ok	✅ done	8178 ms
2026-10-18 10:45 UTC	✅ ok	✅ done	7676 ms
2026-10-18 02:10 UTC	✅ ok	✅ done	7298 ms
2026-10-17 18:05 UTC	✅ ok	✅ done	5765 ms
2026-10-17 09:55 UTC	✅ ok	✅ done	5635 ms
2026-10-17 02:01 UTC	✅ ok	✅ done	6372 ms
2026-10-16 18:40 UTC	✅ ok	✅ done	6308 ms
2026-10-16 11:35 UTC	✅ ok	✅ done	6413 ms
2026-10-16 04:40 UTC	✅ ok	✅ done	5466 ms
2026-10-15 21:45 UTC	✅ ok	✅ done	5458 ms
2026-10-15 14:51 UTC	✅ ok	✅ done	4583 ms
2026-10-15 08:11 UTC	✅ ok	✅ done	4422 ms
2026-10-15 01:40 UTC	✅ ok	✅ done	3941 ms
2026-10-14 19:15 UTC	✅ ok	✅ done	5518 ms
2026-10-14 12:40 UTC	✅ ok	✅ done	4939 ms
2026-10-14 06:16 UTC	✅ ok	✅ done	8792 ms
2026-10-13 23:26 UTC	✅ ok	✅ done	9589 ms
2026-10-13 17:20 UTC	✅ ok	✅ done	10048 ms
2026-10-13 11:16 UTC	✅ ok	✅ done	8200 ms

Method: MCP initialize then tools/list from Faceabot (FaceabotProbe/1.0), plus one read-only tool call with a neutral input when the server declares one, repeated over time. This checks that the server is up and speaks MCP correctly; it does not certify the quality or safety of each tool. How measurement works.

Publisher of Limitguard Lead Verification?

Show your measured reliability on your README or website:

[![Measured by Faceabot](https://faceabot.com/badge/ai.limitguard.api/limitguard.svg)](https://faceabot.com/tools/ai.limitguard.api/limitguard)

Data in JSON: /api/catalog?id=ai.limitguard.api/limitguard · Stop probes: POST /api/reliability/opt-out

AI agents: all of this is available without keys over MCP https://faceabot.com/api/mcp · HTTP https://faceabot.com/api/catalog?q=… · Guide : llms.txt

Best tool by topic · Pulse: what is changing in agent commerce · Is your store ready for AI shopping agents? · State of MCP (weekly) · MCP server doctor · Reliability data · Faceabot app · Faceabot → AI assistants · What AI agents cannot find yet · Add Faceabot to your AI · Badge for tool publishers · Help · Privacy · Terms