Limitguard Lead Verification

Name: Limitguard Lead Verification
Author: jwconsultancyteam

de jwconsultancyteamversión 2.11.9i★ –iSe ejecuta en la nube

Nombre en el registroai.limitguard.api/limitguard

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
Nuestras revisiones básicasi3 de 3 superadasRevisado con información pública; el código aún no se ha escaneado
UsoiAún sin medir★ –

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

Conexión: Se ejecuta en la nube
Transporte: Streamable HTTP
Categoría: Derecho y datos públicos
Debes completar: Authorization

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Revisiones básicas: 3 de 3 superadas
Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
Puede hacer 10 cosas (herramientas) check_entity, get_trust_score, verify_wallet, get_risk_score …
Debes completar tú: Authorization

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

ClaudeClaude CodeCursorVS CodeChatGPT

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Ejecuta esto en tu terminal

claude mcp add --transport http limitguard https://api.limitguard.ai/mcp --header 'Authorization: your-value'

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "limitguard": {
      "url": "https://api.limitguard.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "limitguard": {
      "type": "http",
      "url": "https://api.limitguard.ai/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

Authorization secreto obligatorio HTTP header
Bearer lg_live_... -- the full header value, 'Bearer ' included. Free key: POST https://api.limitguard.ai/v1/keys/create with an email.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 8 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

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, recomme
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_le
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
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
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_na
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 ma
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 x
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.
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
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, t

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026

✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con el dominio api.limitguard.ai (el registro comprueba quién es dueño del dominio)
… Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
… Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
✓ Superada
El endpoint responde
Respondió en 665 ms (HTTP 200)
– No aplica
Inicio de sesión con OAuth
No hace falta iniciar sesión
✓ Superada
Sin instrucciones ocultas en las descripciones de herramientas
Leímos 10 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Derecho y datos públicosi

Más estrellas que el 0% de los otros 1744 servidores de esta categoría
Publicado en el registro más recientemente que el 56% de los otros 1744 servidores de esta categoría
Revisiones básicas iguales o mejores que el 100% de los otros 1744 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Limitguard Lead Verification?

Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: Authorization

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (2.11.9) llegó al registro hace 24 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Romania Company Check, Japan Company Check, U.S. Public Company Check

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Romania Company Check

de JusticeUA

Romania company checks by CUI: status, insolvency, LEI and sanctions from official registers.

Se ejecuta en la nubeActualizado hoy

Instalar

Japan Company Check

de JusticeUA

Japan company checks by corporate number: status, closure cause, successor, LEI and sanctions.

Se ejecuta en la nubeActualizado hoy

Instalar

U.S. Public Company Check

de JusticeUA

U.S. public company checks by SEC CIK: filing status, bankruptcy 8-K flag, LEI and sanctions.

Se ejecuta en la nubeActualizado hoy

Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

Limitguard MCP Server

Check Dutch and Belgian companies, sales leads and crypto wallets before you deal with them, over the Model Context Protocol: the KVK (Netherlands) and KBO (Belgium) registers, EU VAT (VIES), the OFAC, EU and UN sanctions lists and wallet risk on Base and Solana, with the source and date of every answer.

Server URL: https://api.limitguard.ai/mcp Transport: Streamable HTTP (POST) Auth: API key (Bearer), plus an x402 micropayment per call on the free and sandbox tiers

What it is: Limitguard is a lead validation service for lead generation agencies, B2B marketing and sales teams: it checks the company behind each lead against official business registers (full coverage in the Netherlands and Belgium), EU VAT and sanctions lists, with website age in the company check, and returns proceed, review or block with the source on every line. Developers and AI agents can use its HTTP API, MCP server and A2A service, hosted in the EU.

Start here: On MCP a paid tool takes an x402 payment per call, or debits prepaid credit (a paid key, or a funded workspace); wallet_sanctions_preview, sanctions_preview and get_trust_score are free; the free sandbox key returns mock data on the REST API only, not on MCP. Paid by x402: Lead Verify $0.10 per lead and agent check $0.005 per wallet; entity check and KYB $0.29 and risk score $0.25 fresh, $0.11 cached ($0.25 KYB) when available; report $0.55; sanctions and wallet screens $0.005; other routes at the account price. API keys, the dashboard and the Claude connector pay the account prices: Lead Verify $0.27 per lead and agent check $0.75 per wallet; $0.11-1.85 per call; entity and risk checks $0.88-1.05 fresh ($1.50 KYB), $0.11 cached ($0.25 KYB) when available.

Features

Lead verify for Dutch and Belgian sales leads: is it a real, active company? A verdict, a 0-100 lead score and one action per flag ($0.27 with an API key, $0.10 with x402).
Company check against the KVK and KBO registers, EU VAT (VIES), the domain and the IBAN, with a 0-100 score and a recommendation.
Sanctions screen of company and person names against the OFAC, EU and UN lists, with a free yes/no preview.
Crypto wallet screen on Base and Solana: OFAC address match, balances, wallet age, recent activity and risk rules with advice ($0.11 with an API key, $0.005 with x402).
Free wallet sanctions check: a yes/no against the OFAC list.
AI agent wallet check before your agent pays: sanctions, balance, ERC-8004 identity and public reputation ($0.75 with an API key, $0.005 with x402).
Pay per call in USDC on Base or Solana with x402, or with an API key and prepaid credit. A check that fails is not charged.
MCP, REST and A2A, and agents can pay inside A2A with x402.
Sources on every answer, with the date each one was read. Hosted in the EU.

Tools

tools/list is public: connect and read it without any credential. These are the names it returns, and the names tools/call accepts:

Tool	Description	Inputs
`check_entity`	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.	`entity_name` (required), `country` (required), `kvk_number`, `domain`
`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).	`entity_id` (required)
`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.11. Supports EVM and Solana addresses.	`wallet_address` (required), `chain_id`
`get_risk_score`	Quick risk score from sanctions screening and country risk only, without the register or domain lookups of check_entity. 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.	`entity_name` (required), `country` (required)
`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.	`entity_name`, `country`, `kvk_number`, `cbe_number`, `vat_number`, `domain`, `iban`, `wallet_address`, `wallet_chain`, `check_id`
`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.	`name` (required), `country`
`wallet_sanctions_preview`	Free yes/no check of a wallet address against the OFAC SDN list: sanctioned, lists, the list date and its freshness, no programmes or entry ids. 10 per caller per UTC day, separate from sanctions_preview. The full wallet screen is verify_wallet ($0.11).	`wallet_address` (required), `chain_id`
`sanctions_screen`	Sanctions screen against the local OFAC SDN, EU and UN lists: matched entries with list, entry id, programmes, countries, listing date and match score. A name match is not a determination.	`name` (required), `country`
`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.75.	`wallet` (required), `agent_id`, `domain`
`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.27.	`country` (required), `company_number`, `name`, `vat_number`, `email`, `domain`, `address`, `iban`, `phone`, `target_industries`, `target_size`

Pricing

A paid tool call is debited from your API key's prepaid balance at the account price, or paid per call with an x402 micropayment (USDC on Base or Solana) at the agent price in Agent prices (x402). The tools with their own /v1/mcp/* path are priced below at the account price; the other tools are priced at the REST endpoint they call, in Full x402 API.

Endpoint	Account price
Entity Check (`/v1/mcp/check-entity`)	$1.05
Risk Score (`/v1/mcp/risk-score`)	$0.90
Check Agent (`/v1/mcp/check-agent`)	$0.00: hidden placeholder, not in `tools/list`; returns placeholder data
Trust Score (`/v1/mcp/trust-score`)	$0.00, free (your own stored score)
Verify Wallet (`/v1/mcp/verify-wallet`)	$0.11

Authentication

Two things gate a tools/call, in this order:

An API key, as Authorization: Bearer . Without one every call comes back Authentication required. Provide API key via Authorization: Bearer header. Get a free one (no payment, no card):

   curl -X POST https://api.limitguard.ai/v1/keys/create \

-H "Content-Type: application/json" \ -d '{"email": "you@example.com"}'

That returns a free-tier key, which is the key the Quick Start configs below expect. Asking for "tier": "sandbox" instead returns a key that answers with mock data; see the next point before you use one here.

Payment, on the free and sandbox tiers only. Send the x402 proof as PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1), alongside the Bearer key. A key with a prepaid balance (indie and up) is debited per call instead and needs no per-call payment. API keys have no subscription; see API keys and prepaid balance.

A sandbox key does *not* lift the payment requirement on this transport: it owes x402 per call exactly as a free key does, and it answers with mock data rather than a real check. Paying for one over MCP spends real USDC on a mock answer. Where a sandbox key is worth having is the REST mirrors under /v1/mcp/* (sent as X-API-Key, not Bearer), which serve the mock response before the payment check: a way to exercise the request and response shapes, not a cheap source of real checks.

Agent prices (x402)

An x402 payment pays the agent price: REST, A2A with x402, and MCP pay-per-call on /mcp. An API key, the dashboard and the Claude connector pay the account price, from prepaid credit. A route not listed here costs its account price with x402 too.

The official x402 SDKs refuse a payment above one dollar by default (maxAmountPerPayment). That default covers every agent price. Raise it only for the deep-check enhanced and credit tiers and for the /v1/keys/upgrade/* and /v1/keys/topup/* purchases.

Endpoint	Agent price (x402)	Account price
`POST /v1/entity/check`	$0.29 fresh, $0.11 cached	$1.05 fresh, $0.11 cached
`POST /v1/mcp/check-entity`	$0.29	$1.05
`POST /v1/risk/score`	$0.25 fresh, $0.11 cached	$0.90 fresh, $0.11 cached
`POST /v1/mcp/risk-score`	$0.25	$0.90
`POST /v1/kyb/check`	$0.29 fresh, $0.25 cached	$1.50 fresh, $0.25 cached
`POST /v1/reports/entity`	$0.55	$1.85
`POST /v1/leads/verify`	$0.10	$0.27
`POST /v1/agent/check`	$0.005	$0.75
`POST /v1/mcp/verify-wallet`	$0.005	$0.11
`POST /v1/sanctions/screen`	$0.005	$0.11

Full x402 API (direct HTTP)

The tools above are what the MCP server exposes over the Model Context Protocol. Clients that integrate directly over HTTP, instead of through an MCP client, can reach every x402-priced endpoint on https://api.limitguard.ai: the REST endpoints below, plus the MCP tools' own /v1/mcp/* paths. All of them are published in /.well-known/x402.json; /.well-known/mcp.json lists only the tools above.

Most of the REST endpoints are capabilities the MCP tools do not expose, but two run the same engine over plain HTTP: /v1/entity/check behind check_entity (the MCP tool takes the entity name, country, KVK number and domain only, so no IBAN or VAT), and /v1/risk/score behind get_risk_score, at the same price.

Payment is per call throughout: USDC on Base or Solana, at the agent price in Agent prices (x402). The Price columns below are the account prices an API key pays. The data endpoints below need no API key at all. The /v1/keys/upgrade/* endpoints also take payment without one, but they act on an API key you already hold; see API keys and prepaid balance.

Lead and company checks

Endpoint	Method	Price	Description

| `/v1/leads/verif

Solo se muestra el principio; lee el resto en el repo

Limitguard Lead Verification

Resumen

Los tres pilares de PopNx MCP

Qué puedes hacer con él

Instalación

Antes de instalar

Valores que debes completar

Qué puede hacer

Revisiones básicasi

El creador coincide con el repo

Sigue en mantenimiento

Tiene licencia

El endpoint responde

Inicio de sesión con OAuth

Sin instrucciones ocultas en las descripciones de herramientas

Comparado con otros en Derecho y datos públicosi

Preguntas frecuentes

Alternativas

Romania Company Check

Japan Company Check

U.S. Public Company Check

README del creador

Limitguard MCP Server

Features

Tools

Pricing

Authentication

Agent prices (x402)

Full x402 API (direct HTTP)

Lead and company checks