MCP Integration

Connect your AI agents to Diliguard intelligence.

Diliguard natively supports the Model Context Protocol (MCP), letting your AI assistants run corporate intelligence and OSINT modules directly. Works with Claude Desktop, Cursor, and Windsurf.

On this page

How it Works

Instead of writing scripts or manually pinging our API, you can now simply ask your AI:

We provide an official Node.js MCP server package: @sluxia/diliguard-mcp. You can run this package locally using npx, and it will securely connect your AI assistant to your Diliguard account.

Because the package runs locally on your machine, your DILIGUARD_API_KEY is securely stored in your own environment variables and is never exposed in URLs or logged by external proxies.

Available AI Tools

Once connected, your AI assistant will automatically discover the following Diliguard tools:

1. run_corporate_kyc: Runs LEI, UBO, Sanctions, Regulatory, Adverse Media, Offshore Leaks, Domain, VAT, and IBAN checks.
2. run_person_trace: Runs PEP/Interpol, Regulatory, Sanctions, Person Adverse Media, Email OSINT, Phone, Username, and Dark Web checks.
3. run_crypto_investigation: Runs Wallet Sanctions, Illicit/Mixer tracing, Activity, and IP Intelligence checks.
4. run_vendor_risk: Evaluates multiple companies concurrently for LEI, UBO, Sanctions, Regulatory Fines, Corporate Adverse Media, and Offshore Leaks.
5. run_ultimate_fraud: Holistic EDD snapshot combining Corporate and Person parameters (triggers all relevant modules).
6. run_aml_pep_screening: Institutional AML screening across Sanctions, PEP/Interpol, Adverse Media, Regulatory Fines, and Offshore Leaks.
7. run_registry_check: Verifies LEI corporate registration, UBO ownership, and Offshore tax haven leaks.
8. run_ip_intelligence: Investigates IP addresses, WHOIS/DNS domain infrastructure, and network risk signals.
9. run_transaction_scoring: Evaluates transaction risk by combining IP Intelligence, Email OSINT, Dark Web Leaks, Illicit Crypto, and IBAN Validation.

Setup Instructions (Claude Desktop)

To connect your local Claude Desktop app to Diliguard’s intelligence engine, update your claude_desktop_config.json file.

1. Open your Claude Desktop configuration:

1. Add the Diliguard mcpServer entry using the npx command. Be sure to insert your own personal Admin Key:

{
  "mcpServers": {
    "diliguard": {
      "command": "npx",
      "args": ["-y", "@sluxia/diliguard-mcp"],
      "env": {
        "DILIGUARD_API_URL": "https://api.diliguard.com",
        "DILIGUARD_API_KEY": "YOUR_PERSONAL_ADMIN_KEY"
      }
    }
  }
}

1. Restart Claude Desktop. You should now see a small “plug” icon or “Diliguard” listed under your available MCP tools.

Testing with the MCP Inspector

If you want to debug the connection before adding it to Claude, you can use the official Model Context Protocol Inspector:

DILIGUARD_API_URL="https://api.diliguard.com" DILIGUARD_API_KEY="YOUR_KEY" npx @modelcontextprotocol/inspector npx -y @sluxia/diliguard-mcp

This will spin up a local web UI where you can view our tools and execute test payloads directly against the Diliguard backend.

Next Steps