LimitGuard MCP Server

Trust Intelligence for AI agents. Entity verification, sanctions screening, and risk scoring via the Model Context Protocol.

Server URL: https://api.limitguard.ai/mcp Transport: Streamable HTTP (POST) Auth: API key (Bearer), plus an x402 micropayment per call on the free tier

Tools

tools/list is public — connect and read it without any credential. These are the names it returns, and the names tools/call accepts:

Related MCP server: Concept-4 Compliance Engine

Pricing

All tools are priced via x402 micropayments (USDC on Base or Solana):

Authentication

Two things gate a tools/call, in this order:

1. An API key, as Authorization: Bearer <key>. Without one every call comes back Authentication required. Provide API key via Authorization: Bearer <lg_live_...> 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", "tier": "sandbox"}'

2. Payment, on the free and sandbox tiers only. Send the x402 proof as PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1), alongside the Bearer key. A paid subscription (indie and up) covers usage and needs no per-call payment.

   A sandbox key does not lift the payment requirement on this transport. It does on the REST mirrors under /v1/mcp/* (sent as X-API-Key, not Bearer), which is the cheapest way to try the tools before wiring up payment.

Full x402 API (direct HTTP)

The 5 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 18 x402-priced endpoints on https://api.limitguard.ai: the 13 REST endpoints below, plus the MCP tools' own /v1/mcp/* paths. All 18 are published in /.well-known/x402.json; only the 5 tools above are listed by /.well-known/mcp.json.

Most of the REST endpoints are capabilities the MCP tools do not expose, but two are the same check reached over plain HTTP: /v1/entity/check behind check_entity — the manifest describes /v1/mcp/check-entity as "same as /v1/entity/check with MCP-native interface" — and /v1/risk/score behind risk_score, at the same $0.65.

Payment works the same way throughout: USDC on Base or Solana, pay-per-call. The 9 data endpoints below need no API key at all. The 4 /v1/keys/upgrade/* endpoints also take payment without one, but they act on an API key you already hold — see API key tiers.

Trust intelligence

Reputation management

Wallet services

Regulatory compliance

MCP tool paths (direct HTTP)

The 5 MCP tools are also reachable over plain HTTP at their own x402-priced paths — same capabilities and prices as the Tools table above, for clients that pay per call without opening an MCP session.

API key tiers

LimitGuard accepts two forms of payment: x402 per call — which needs no API key, as everywhere else in this README — or an API key carrying a monthly call allowance. A base key is free and self-service: POST /v1/keys/create with an email address, no payment and no existing key needed. The endpoints below take a one-time x402 payment to raise that key's monthly allowance.

Prices and descriptions above mirror the live x402 manifest as of 2026-09-05. The manifest is the source of truth — fetch it if you need the current schema for any endpoint.

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "limitguard": {
      "type": "url",
      "url": "https://api.limitguard.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_LIMITGUARD_KEY"
      }
    }
  }
}

Cursor

Add to MCP settings:

{
  "limitguard": {
    "type": "url",
    "url": "https://api.limitguard.ai/mcp",
    "headers": {
      "Authorization": "Bearer YOUR_LIMITGUARD_KEY"
    }
  }
}

Smithery

npx -y @smithery/cli install @limitguard/trust-intelligence

Any MCP Client

Connect to https://api.limitguard.ai/mcp using Streamable HTTP transport (POST), sending Authorization: Bearer <key> on every tools/call.

Discovery Endpoints

Use Cases

• KYC/KYB Automation — AI agents verify business entities before transactions

• Sanctions Screening — Check entities against OpenSanctions watchlists

• Agent-to-Agent Trust — Verify counterparty agent reputation before collaboration

• Wallet Verification — Check blockchain wallet risk before on-chain transactions

• Due Diligence — Automated entity research with trust scoring

Security

• HTTPS with TLS 1.3

• x402 payment protocol for per-call billing (no stored payment credentials)

• GDPR-compliant (EU-hosted, data minimization)

• All tools are read-only (no data modification)

• Rate limited per payment (abuse-proof)

Links

• Website: limitguard.ai

• Status: status.limitguard.ai

• MCP Registry: ai.limitguard.api/trust-intelligence

License

MIT