MCP.so
Sign In

Limitguard MCP Server

@jwconsultancyteam

Basic information

Category

Other

Last updated

License

MIT

Author

jwconsultancyteam

About Limitguard MCP Server

Limitguard MCP server: lead validation for AI agents. Checks the company behind a lead in the Dutch (KVK) and Belgian (KBO) registers, EU VAT (VIES) and sanctions lists. Pay per call with x402 or an API key.

Limitguard MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "limitguard": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/jwconsultancyteam/limitguard-mcp",
        "limitguard-mcp"
      ],
      "env": {
        "LIMITGUARD_API_KEY": "YOUR_LIMITGUARD_KEY"
      }
    }
  }
}

Limitguard MCP Server tools

10

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.

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).

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.

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.

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.

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.

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).

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.

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.

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.

Overview

What is Limitguard?

Limitguard MCP server: lead validation for AI agents. Checks the company behind a lead in the Dutch (KVK) and Belgian (KBO) registers, EU VAT (VIES) and sanctions lists. Pay per call with x402 or an API key.

How to use Limitguard?

The README includes setup instructions such as npx -y @smithery/cli install team-mehs/limitguard.

Key features of Limitguard

  • Sanctions screen of company and person names against the OFAC, EU and UN lists, with a free yes/no preview
  • Free wallet sanctions check: a yes/no against the OFAC list
  • 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
  • Claude Code (all three skills plus the MCP server, OAuth sign-in)

Use cases of Limitguard

  • Connect an MCP-compatible client to this repository's service.
  • Review the README-backed setup before enabling it in production.

Frequently asked questions

1

Where is the source code for Limitguard?

The source code is linked from the repository URL on this page.

2

Does Limitguard include a standard MCP config?

If the README contains a parseable MCP configuration block, it is shown in the Config tab.

Comments

More Other MCP servers