mcpbeat Sign in

Limitguard Lead Verification MCP Server

answering

Limitguard Lead Verification is answering right now. Last checked 12 min ago. It exposes 10 tools. Last commit 14 Oct 2026.

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

Uptime history 5 days of history · worst day 97%
5 days agonow
98.9%
Uptime 24h
91 of 92 checks
10
Tools
read from the server
211 ms
Response time
average over 24h
1
Stars
last commit 14 Oct 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.

14 Oct 4 tool descriptions were rewritten check_agent_wallet, verify_lead, verify_wallet and 1 more

Limitguard Lead Verification does not always answer

Over the last week it answered 98.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add limitguard --transport http https://api.limitguard.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "limitguard": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.limitguard]
url = "https://api.limitguard.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "limitguard": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "limitguard": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}

Available tools 10

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

sanctions
sanctions_preview
Free yes/no sanctions preview against the local OFAC SDN, EU and UN lists. Returns possible_match, lists_checked, list_dates and list_note only, never an entry. 10 per caller per UTC day, shared with POST /v1/sanctions/preview, and key holders share a ceiling of 50 per IP; the matched entries are the sanctions_screen tool. Free ($0). Args: name: Company or person name to screen country: Optional ISO 3166-1 alpha-2 country code (orders matches, never excludes one)
sanctions_screen
Sanctions screen against the local OFAC SDN, EU and UN lists: matched entries. Each match carries its list, entry id, entry type, programmes, countries, listing date and match score (exact normalised or word-order-insensitive name match only). A name match is not a determination. Rejected calls are not charged. Args: name: Company or person name to screen country: Optional ISO 3166-1 alpha-2 country code (orders matches, never excludes one)
verify
verify_lead
Verify a NL/BE sales lead against the registers in one call: real and active, VAT, mail server, IBAN, sanctions; a 0-100 lead score. $0.10 by x402, $0.27 with an API key. Returns verdict (real_active, real_inactive, not_found, ambiguous, unverifiable or sanctioned), lead_score, the company as registered, and the vat, iban, sanctions and email checks, with flags and one finding per flag or mismatch, a dormant-shell score and, when a target is given, the ICP fit (information only). An input not given is not checked and never counts against the lead. The IBAN account holder is not checked. BE needs company_number. Rejected calls are not charged. Args: country: NL (KVK) or BE (KBO) company_number: 8-digit KVK number or 10-digit KBO/CBE number name: Company name as the lead gave it (NL without a number) vat_number: EU VAT number, checked with VIES email: Contact email; only its domain is checked domain: Company website domain address: {street, house_number, postcode, city} the lead gave iban: IBAN the lead gave; only country, bank, BIC and last 4 are returned phone: Phone number the lead gave; compared with the numbers the company publishes, never echoed. Rejected until website phone lookup is switched on target_industries: Ideal-customer industries: SBI/NACE code prefixes ("62") or whole words; information only target_size: Ideal-customer employee range {min, max}, both inclusive; information only
verify_wallet
Screen a wallet: OFAC SDN address match, on-chain signals (contract check, native and USDC balance, transaction count, first seen on Base) and named risk rules with up to 3 advice items. On Base, also reports any ERC-8004 agent the wallet owns and its open on-chain reputation as descriptive signals, never scored. $0.005 by x402, $0.11 with an API key. Returns risk_score, risk_level, sanctions (hit, lists, as_of), signals with their source, the names of signals that could not be read (unavailable), rules_fired, advice and linked_entities (entities you checked that were linked to this wallet). On Base, also erc8004_agent_ids and erc8004_reputation (open ERC-8004 feedback, descriptive only -- never folded into risk_score or advice). Accepts EVM (0x...) and Solana (base58) addresses. The sanctions match alone is free: the wallet_sanctions_preview tool. Rejected calls are not charged. Args: wallet_address: Blockchain wallet address chain_id: CAIP-2 chain ID (default: eip155:8453 for Base); base, eth, solana, btc also accepted
agent
check_agent_wallet
Check a counterparty agent's EVM wallet in one call: OFAC SDN digital-currency address list match, Base USDC and ETH balance, ERC-8004 identity registration (and, given an agent id, that agent's owner and payment wallet) and open ERC-8004 feedback, which is not scored. $0.005 by x402, $0.75 with an API key. Returns verdict (block, review or no_findings) with verdict_reasons, the components that ran and those that did not (with a reason), and sanctions, balance, identity, reputation, wallet_risk and domain (when a domain is given, else not_requested), each with its own status (ok, unavailable or error). Reputation and domain are descriptive only and never change the verdict. Base only; EVM addresses only. Args: wallet: EVM wallet address (0x + 40 hex characters) agent_id: Optional ERC-8004 agentId (decimal) the wallet claims domain: Optional website domain the agent gives for itself (e.g. example.com)
compliance
get_compliance_report
Per-entity report built from one real check. Registry identity, sanctions and PEP screens, domain signals, risk score with the rules that fired, correlations, every finding as a ranked action, a per-source status table (ok / unavailable / error) and a report hash. Args: entity_name: Full legal name (with country; omit when sending check_id) country: ISO 3166-1 alpha-2 country code kvk_number: Optional Dutch KVK number (8 digits) cbe_number: Optional Belgian CBE number (0XXX.XXX.XXX or 10 digits) vat_number: Optional EU VAT number domain: Optional company website domain iban: Optional IBAN (never stored raw) wallet_address: Optional crypto wallet address (format check only) wallet_chain: Optional chain for wallet_address (eth, base, btc, sol, ...) check_id: Id of a check from an earlier report, instead of identifiers
entity
check_entity
Company check via the Limitguard API. Company check on a business: sanctions screening and country risk, the Dutch KVK register for an NL company, and the website domain when you send it. Returns trust_score (0-100, 100 = best), trust_level (high means low risk), cluster, recommendation, confidence, top_factors and sources_checked. Args: entity_name: Full legal name of the entity country: ISO 3166-1 alpha-2 country code (e.g., NL, BE, DE) kvk_number: Optional Dutch KVK registration number (8 digits) domain: Optional company website domain
risk
get_risk_score
Quick risk score from sanctions screening and country risk only. Faster than check_entity: no register or domain lookup. Use when you only need basic risk evaluation. Returns risk_score (0-100, 100 = riskiest), risk_level (high means high risk, the reverse of check_entity's trust_level), sanctions_match and fatf_status; no recommendation or factors. Args: entity_name: Full legal name of the entity country: ISO 3166-1 alpha-2 country code
trust
get_trust_score
Look up your own most recent trust score for an entity you checked before, from your stored checks: score, level, when, which product, trend and how many checks are on record. Runs no new check and calls no data source. Free ($0). Returns status "found" with trust_score, trust_level, checked_at, source_product, trend and checks_on_record, or status "not_found" with a next_step. Only checks made with your key (via check_entity, or REST entity/KYB checks) are read; another key's or workspace's never are (#946). Signed in with OAuth, your workspace's checks are read instead (#1062). Args: entity_id: The entity name, as you sent it to check_entity
wallet
wallet_sanctions_preview
Free yes/no check of a wallet address against the OFAC SDN list. Returns wallet_address (canonical), chain_id, sanctioned, lists, as_of (the list's publication date), status (ok or stale), source and upgrade, which names the full wallet screen (the verify_wallet tool, $0.005 by x402, $0.11 with an API key: balances, wallet age and activity, contract and delegation checks, a risk score with rules and advice, linked entities, ERC-8004 identity and reputation). 10 per caller per UTC day, shared with POST /v1/sanctions/wallet and separate from the name preview; key holders share a ceiling of 50 per IP. Free ($0). Args: wallet_address: Blockchain wallet address chain_id: CAIP-2 chain ID (default: eip155:8453 for Base); base, eth, solana, btc also accepted

Endpoints

URLTransportStateLatencyChecked
https://api.limitguard.ai/mcp streamable-http answering 217 ms 12 min ago

Alternatives to Limitguard Lead Verification

same job, measured the same way
Limitguard Lead Verification
by limitguard-api

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

10 tools answering
Leadloadz
by ali1041

B2B lead search and email verification MCP server

43 installs/wk local only
ClearBounce Email Verification
by clearbounce

Verify email addresses in real time and find business email addresses with live mailbox checks.

5 tools answering
Commsharbor
by commsharbor

Domain email and webmail: set up domains, mailboxes and aliases, and check DNS verification.

32 tools answering
Kawaa email verification
by kawaa

Check whether an email address can receive mail, one address or a list, without sending to it.

answering
SureCheck MCP
by killfear1

Local stdio phone metadata and email syntax/DNS checks. Not live carrier or mailbox verification.

local only
MCP Enrichment
by intelagentstudios

Multi-source entity enrichment: company data, contacts, email verification, and phone validation

58 installs/wk local only
Snov MCP Server
by snov

Snov.io: lead discovery, email verification, enrichment, CRM, and LinkedIn automation actions.

answering

Limitguard Lead Verification — questions

Answers built from our own checks of this server.

What can Limitguard Lead Verification do?
It exposes 10 tools, read directly from the server on our last check. Among them: check_agent_wallet, check_entity, get_compliance_report, get_risk_score, get_trust_score, sanctions_preview and 4 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 →
What is Limitguard Lead Verification mostly used for?
Its tools cluster around sanctions and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Limitguard Lead Verification working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 211 ms. The bar chart above shows every period we have measured.
How do I connect Limitguard Lead Verification?
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 Limitguard Lead Verification need an API key?
No. Limitguard Lead Verification completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Limitguard Lead Verification?
It answers our handshake in 211 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 Limitguard Lead Verification open source?
Yes — it is published under the MIT licence, written in Python and 1 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.