Limitguard Trust Intelligence MCP MCP server

An MCP server providing entity verification, sanctions screening, and trust scoring for AI agents. It validates leads against official business registers, EU VAT lists, and sanctions, returning proceed, review, or block decisions. It supports x402 micropayments for live usage and offers a free sandbox for testing.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Limitguard

MCP endpoint (Streamable HTTP)

https://api.limitguard.ai/mcp

Vendor documentation

What you can do with it

Verify company legitimacy against official business registers
Screen entities against EU VAT and sanctions lists
Perform KYB checks for lead generation agencies
Integrate trust scoring into AI agent workflows

Tools advertised by the last live check:

check_entity
get_trust_score
verify_wallet
get_risk_score
get_compliance_report
sanctions_preview
sanctions_screen
check_agent_wallet
verify_lead

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http limitguard-trust-intelligence-mcp https://api.limitguard.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add limitguard-trust-intelligence-mcp --url https://api.limitguard.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable limitguard-trust-intelligence-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "limitguard-trust-intelligence-mcp": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "limitguard-trust-intelligence-mcp": {
      "type": "streamableHttp",
      "url": "https://api.limitguard.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start limitguard-trust-intelligence-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "limitguard-trust-intelligence-mcp": {
      "type": "http",
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http limitguard-trust-intelligence-mcp https://api.limitguard.ai/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "limitguard-trust-intelligence-mcp": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "limitguard-trust-intelligence-mcp": {
      "serverUrl": "https://api.limitguard.ai/mcp"
    }
  }
}

See all 347

Do you run Limitguard Trust Intelligence MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing