mcpbeat

LimitGuard Trust Intelligence MCP Server

ai.limitguard.api/trust-intelligence
not responding

LimitGuard Trust Intelligence is listed as active in the registry but did not answer our last check.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 42 hours of history · worst hour 0%
42 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
207 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add trust-intelligence --transport http https://api.limitguard.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "trust-intelligence": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.trust-intelligence]
url = "https://api.limitguard.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trust-intelligence": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "trust-intelligence": {
      "url": "https://api.limitguard.ai/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://api.limitguard.ai/mcp streamable-http answering 207 ms 13 min ago

LimitGuard Trust Intelligence — questions

Answers built from our own checks of this server.

Is LimitGuard Trust Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 207 ms. The bar chart above shows every period we have measured.
Is LimitGuard Trust Intelligence still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists LimitGuard Trust Intelligence as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect LimitGuard Trust Intelligence?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does LimitGuard Trust Intelligence need an API key?
No. LimitGuard Trust Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.