Lintsure
Compliance readiness checks for code: EU AI Act, GDPR, SOC 2, ISO 27001. Local. Not legal advice.
作者による説明(英語の原文)
Lead validation over MCP: KVK/KBO register, EU VAT, sanctions and email checks with sources.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
Authorization「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
このアドレスはリクエストの header にキーが必要ですが、コネクタを追加するメニューでは設定できません。代わりにClaude Code、Cursor、VS Codeを使ってください。
ターミナルでこれを実行します
claude mcp add --transport http limitguard https://api.limitguard.ai/mcp --header 'Authorization: your-value'動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"limitguard": {
"url": "https://api.limitguard.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .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この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
ツールの名前と説明は、サーバーが2026年11月8日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
check_entityCompany 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_scoreLook 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_walletScreen 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_scoreQuick 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_reportPer-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_previewFree 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_previewFree 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_screenSanctions 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_walletCheck 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_leadVerify 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
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック
レジストリ名はドメイン api.limitguard.ai で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
665ミリ秒で応答(HTTP 200)
サインイン不要
10件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:Authorization
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は–、最新バージョン(2.11.9)がレジストリに届いたのは24 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Lintsure, Premium Data MCP Server, Patents Trademarks Ip MCP Server
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Compliance readiness checks for code: EU AI Act, GDPR, SOC 2, ISO 27001. Local. Not legal advice.
Government contracts, business registration, FDA recalls and product-price data as agent tools.
Patent search, inventor search, patents-by-assignee and full patent detail as agent tools.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
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 |
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 |
Two things gate a tools/call, in this order:
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-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.
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 |
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.
| Endpoint | Method | Price | Description |
|---|
| `/v1/leads/verif
冒頭だけを表示しています。続きはリポジトリで読めます