Limitguard Lead Verification
REMOTE · API.LIMITGUARD.AI
Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources.
Available components
Last scanned (13 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2288 tokens (~228/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Tool “check_agent_wallet” rewrote its description, which is the text the model reads security
- Tool “verify_lead” rewrote its description, which is the text the model reads security
- Tool “verify_wallet” rewrote its description, which is the text the model reads security
- Tool “wallet_sanctions_preview” rewrote its description, which is the text the model reads security
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://api.limitguard.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=limitguard.ai | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c2f01c33f01c684d0eef50799c1fdf2a |
| SANs: limitguard.ai, *.limitguard.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.limitguard.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| limitguard.ai. | present | 2371 | 13 | Verified |
| api.limitguard.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.limitguard.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.limitguard.ai/mcp | HTTPS enforced | 308 | https://api.limitguard.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_agent_wallet ~265
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)
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | – | – |
| domain | – | – | – |
| wallet | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_entity ~177
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
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| domain | – | – | – |
| entity_name | string | yes | – |
| kvk_number | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_compliance_report ~279
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
| Name | Type | Req | Description |
|---|---|---|---|
| cbe_number | – | – | – |
| check_id | – | – | – |
| country | – | – | – |
| domain | – | – | – |
| entity_name | – | – | – |
| iban | – | – | – |
| kvk_number | – | – | – |
| vat_number | – | – | – |
| wallet_address | – | – | – |
| wallet_chain | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_risk_score ~137
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
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| entity_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_trust_score ~181
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
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sanctions_preview ~143
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)
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sanctions_screen ~131
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)
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_lead ~440
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
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| company_number | – | – | – |
| country | string | yes | – |
| domain | – | – | – |
| – | – | – | |
| iban | – | – | – |
| name | – | – | – |
| phone | – | – | – |
| target_industries | – | – | – |
| target_size | – | – | – |
| vat_number | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_wallet ~300
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
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | – | – |
| wallet_address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
wallet_sanctions_preview ~235
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
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | – | – |
| wallet_address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Limitguard Lead Verification MCP server?
Limitguard Lead Verification is a hosted endpoint at https://api.limitguard.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.limitguard.ai
claude mcp add --transport http ai-limitguard-api-limitguard 'https://api.limitguard.ai/mcp'
What is the Limitguard Lead Verification MCP server?
Limitguard Lead Verification is an MCP server listed in the public MCP registry as ai.limitguard.api/limitguard. Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources. This page covers its hosted endpoint (https://api.limitguard.ai/mcp).
Is the Limitguard Lead Verification MCP server safe to use?
Limitguard Lead Verification scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Limitguard Lead Verification MCP server expose?
Limitguard Lead Verification exposes 10 tools: check_entity, get_trust_score, verify_wallet, get_risk_score, get_compliance_report, and 5 more. Their descriptions and schemas cost roughly 2,288 tokens of context every time the server is loaded.
Does the Limitguard Lead Verification MCP server require authentication?
No. We connected to Limitguard Lead Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Limitguard Lead Verification MCP server still maintained?
Limitguard Lead Verification is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.