LimitGuard Trust Intelligence
REMOTE · API.LIMITGUARD.AI · SCANNED SEP 20
Entity verification, sanctions screening, and trust scoring for AI agents via x402 micropayments.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 549 tokens (~109/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the LimitGuard Trust Intelligence MCP server?
LimitGuard Trust Intelligence is a hosted endpoint at https://api.limitguard.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.limitguard.ai
claude mcp add --transport http ai-limitguard-api-trust-intelligence 'https://api.limitguard.ai/mcp'
{
"mcpServers": {
"ai-limitguard-api-trust-intelligence": {
"url": "https://api.limitguard.ai/mcp"
}
}
} {
"servers": {
"ai-limitguard-api-trust-intelligence": {
"type": "http",
"url": "https://api.limitguard.ai/mcp"
}
}
} [mcp_servers.ai-limitguard-api-trust-intelligence] url = "https://api.limitguard.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-limitguard-api-trust-intelligence": {
"type": "remote",
"url": "https://api.limitguard.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-limitguard-api-trust-intelligence --url 'https://api.limitguard.ai/mcp' --transport streamable-http
mcp_servers:
ai-limitguard-api-trust-intelligence:
url: "https://api.limitguard.ai/mcp" {
"McpServers": {
"ai-limitguard-api-trust-intelligence": {
"Transport": "http",
"Url": "https://api.limitguard.ai/mcp"
}
}
} assistant mcp add ai-limitguard-api-trust-intelligence -t streamable-http -u 'https://api.limitguard.ai/mcp'
{
"mcpServers": {
"ai-limitguard-api-trust-intelligence": {
"type": "http",
"url": "https://api.limitguard.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +3
- HSTS header: fail → pass ▲ security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- HSTS header: pass → fail ▼ security
- Server version: 1.29.1 → 1.30.0 functional
- 8 Sept 26 −1
- Tool “check_agent” rewrote its description, which is the text the model reads security
- Tool “get_trust_score” rewrote its description, which is the text the model reads security
- Tool “verify_wallet” rewrote its description, which is the text the model reads security
- Schema quality: 89 → 109 ▼ functional
- Schema quality: excellent → good functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.limitguard.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=limitguard.ai | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c2f01c33f01c684d0eef50799c1fdf2a |
| SANs: limitguard.ai, *.limitguard.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.limitguard.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| limitguard.ai. | present | 2371 | 13 | Verified |
| api.limitguard.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.limitguard.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.limitguard.ai/mcp | HTTPS enforced | 308 | https://api.limitguard.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_agent ~112
Unimplemented / beta: returns placeholder data, not a real result. Free ($0) until real logic ships. Verify AI agent trust via LimitGuard. Today every call returns verified=false, trust_score=0 and status="unimplemented" regardless of input (#206). Intended for multi-agent systems to verify delegation targets. Args: agent_id: Unique agent identifier agent_name: Human-readable agent name
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| agent_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_entity ~131
Check 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 country code (e.g., NL, BE, DE) kvk_number: Optional Dutch KVK registration number (8 digits) domain: Optional company website domain
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| domain | – | – | – |
| entity_name | string | yes | – |
| kvk_number | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_risk_score ~83
Quick 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
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| entity_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_trust_score ~92
Unimplemented / beta: returns placeholder data, not a real result. Free ($0) until real logic ships. Quick trust score lookup by entity ID. Today every call returns trust_score=0 and trust_level="unknown" regardless of input (#206). Args: entity_id: Entity identifier (KVK number, domain, or hash)
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
verify_wallet ~131
Unimplemented / beta: returns placeholder data, not a real result. Free ($0) until real logic ships. Check wallet trust score for crypto payments. Today every call returns risk_score=0 and scam_probability=0.0 regardless of input (#206). Accepts EVM (0x...) and Solana (base58) addresses. Args: wallet_address: Blockchain wallet address chain_id: CAIP-2 chain ID (default: eip155:8453 for Base)
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | – | – |
| wallet_address | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the LimitGuard Trust Intelligence MCP server?
LimitGuard Trust Intelligence is an MCP server listed in the public MCP registry as ai.limitguard.api/trust-intelligence. Entity verification, sanctions screening, and trust scoring for AI agents via x402 micropayments. This page covers its hosted endpoint (https://api.limitguard.ai/mcp).
Is the LimitGuard Trust Intelligence MCP server safe to use?
LimitGuard Trust Intelligence scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LimitGuard Trust Intelligence MCP server expose?
LimitGuard Trust Intelligence exposes 5 tools: check_entity, check_agent, get_trust_score, verify_wallet, get_risk_score. Their descriptions and schemas cost roughly 549 tokens of context every time the server is loaded.
Does the LimitGuard Trust Intelligence MCP server require authentication?
No. We connected to LimitGuard Trust Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LimitGuard Trust Intelligence MCP server still maintained?
LimitGuard Trust Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.