Limitguard Lead Verification

Name: Limitguard Lead Verification
Author: jwconsultancyteam

作者：jwconsultancyteam版本 2.11.9i★ –i在云端运行

注册名称ai.limitguard.api/limitguard

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 聊天与邮件
你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

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

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 api.limitguard.ai 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“聊天与邮件”中的其他服务器比较i

星标数多于此分类中其他 1765 个服务器的 0%
发布到注册中心的时间比此分类中其他 1765 个服务器的 55% 更新
基础检查结果等于或优于此分类中其他 1765 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Limitguard Lead Verification 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：Authorization

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.11.9）于23天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Vexa, emailmd, MCP WhatsApp Cloud

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Vexa

作者：Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

在云端运行★ 2,949Apache-2.02个月前更新

安装

emailmd

作者：anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

电脑或云端★ 1,385MIT31天前更新

安装

MCP WhatsApp Cloud

作者：codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

在你的电脑上运行★ 277MIT5个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读