Index / MCP servers / Limitguard Lead Verification

Limitguard Lead Verification MCP server

Connect Limitguard Lead Verification and your agent gets 5 tools, among them check_agent, check_entity, get_risk_score. It answers at https://api.limitguard.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 9 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.

Status
Answering
Tools
5
Official
yes, served from limitguard.ai
Reliability
9 of 10 checks
Response time
164 ms
Transport
streamable HTTP
Last checked
17 October 2026

Entity verification, sanctions screening, and trust scoring for AI agents via x402 micropayments.

Description as the publisher wrote it.

The 5 tools Limitguard Lead Verification offers

ToolWhat it does
check_agentVerify AI agent trust via LimitGuard. Checks if an AI agent is trusted based on its identifier. Used for multi-agent systems to verify delegation targets. Args: agent_id: Unique agent identifier agent_name: Human-readable agent name
Inputs: agent_id, agent_name
check_entityCheck entity trust score via LimitGuard API. Full trust intelligence check on a business entity. Returns trust score (0-100), risk level, and recommendation. Args: entity_name: Full legal name of the entity country: ISO 3166-1 alpha-2 count
Inputs: entity_name, country, kvk_number, domain
get_risk_scoreQuick risk assessment without full trust check. Faster endpoint that focuses on risk signals only. Use when you only need basic risk evaluation. Args: entity_name: Full legal name of the entity country: ISO 3166-1 alpha-2 country code
Inputs: entity_name, country
get_trust_scoreQuick trust score lookup by entity ID. Fast lookup for previously checked entities. Returns cached score if available. Args: entity_id: Entity identifier (KVK number, domain, or hash)
Inputs: entity_id
verify_walletCheck wallet trust score for crypto payments. Verifies wallet against scam lists and transaction patterns. Supports EVM (0x...) and Solana (base58) addresses. Args: wallet_address: Blockchain wallet address chain_id: CAIP-2 chain ID (defaul
Inputs: wallet_address, chain_id

Add Limitguard Lead Verification to your AI client

Every block below points at https://api.limitguard.ai/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http limitguard-lead-verification https://api.limitguard.ai/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "limitguard-lead-verification": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.limitguard.ai/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "limitguard-lead-verification": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "limitguard-lead-verification": {
      "type": "http",
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "limitguard-lead-verification": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "limitguard-lead-verification": {
      "serverUrl": "https://api.limitguard.ai/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "limitguard-lead-verification": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Limitguard Lead Verification
version: 0.0.1
schema: v1
mcpServers:
  - name: Limitguard Lead Verification
    type: streamable-http
    url: https://api.limitguard.ai/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "limitguard-lead-verification": {
      "httpUrl": "https://api.limitguard.ai/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "limitguard-lead-verification": {
      "type": "http",
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "limitguard-lead-verification": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapi.limitguard.ai%2Fmcp&type=streamable_http&id=limitguard-lead-verification&name=Limitguard%20Lead%20Verification

Is Limitguard Lead Verification up right now?

It answered our last check on 17 October 2026 in 164 ms. Over 10 checks since 4 September 2026 it answered 9. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Limitguard Lead Verification

Questions about Limitguard Lead Verification

Is there an official Limitguard Lead Verification MCP server?

Yes. It is published by limitguard.ai and served from api.limitguard.ai, the vendor's own domain: https://api.limitguard.ai/mcp.

How many tools does Limitguard Lead Verification have?

5, as returned by the server's own tools/list on 6 September 2026: check_agent, check_entity, get_risk_score, get_trust_score, verify_wallet.

Is Limitguard Lead Verification down?

It answered our last check on 17 October 2026 in 164 ms. Over 10 checks since 4 September 2026 it answered 9.

How do I add Limitguard Lead Verification to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.limitguard.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Limitguard Lead Verification need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: ai.limitguard.api. Endpoint host: api.limitguard.ai. ARD identifier: urn:air:ai.limitguard.api:mcp:trust-intelligence. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.