Limitguard Trust Intelligence by api.limitguard.ai
MCP server · Payment & monetisation platforms · indexed, not reviewed
Hostedvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Entity verification, sanctions screening, and trust scoring for AI agents via x402 micropayments.
Facts
- MCP registry
ai.limitguard.api/trust-intelligence· 2.4.1- Endpoint
https://api.limitguard.ai/mcp- Website
- limitguard.ai
- GitHub stars
- 1
- Registry entry
- updated 4 Oct 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under api.limitguard.ai, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 9 · about 3,516 tokens of context · checked 4 hours ago
| Tool | What it does | Hint |
|---|---|---|
check_entity | 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… | read-only |
get_trust_score | Look up your own most recent trust score for an entity you checked before, from your stored checks: score, level, when, which product, trend and how many checks are on record. Runs no new check and calls no data source.… | read-only |
verify_wallet | Screen a wallet: OFAC SDN address match, on-chain signals (contract check, native and USDC balance, transaction count, first seen on Base) and named risk rules with up to 3 advice items. On Base, also reports any… | read-only |
get_risk_score | 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… | read-only |
get_compliance_report | Per-entity report built from one real check. Registry identity, sanctions and PEP screens, domain signals, risk score with the rules that fired, correlations, every finding as a ranked action, a per-source status table… | writes |
sanctions_preview | Free yes/no sanctions preview against the local OFAC SDN, EU and UN lists. Returns possible_match, lists_checked and list_dates only, never an entry. 10 per caller per UTC day, shared with POST /v1/sanctions/preview,… | read-only |
sanctions_screen | Sanctions screen against the local OFAC SDN, EU and UN lists: matched entries. Each match carries its list, entry id, entry type, programmes, countries, listing date and match score (exact normalised or… | read-only |
check_agent_wallet | Check a counterparty agent's EVM wallet in one call: OFAC SDN digital-currency address list match, Base USDC and ETH balance, ERC-8004 identity registration (and, given an agent id, that agent's owner and payment… | read-only |
verify_lead | Verify a NL/BE sales lead against the registers in one call: real and active, VAT, mail server, IBAN, sanctions; a 0-100 lead score. $0.27. Returns verdict (real_active, real_inactive, not_found, ambiguous, unverifiable… | read-only |
What https://api.limitguard.ai/mcp answered to tools/list, asked without credentials over MCP 2025-11-25. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 0 warnings · 10 notes
- noteTC11check_agent_walletparameters are documented in the description but not in the schema: agent_id, domain, wallet
- noteTC11check_entityparameters are documented in the description but not in the schema: country, domain, entity_name, kvk_number
- noteTC11get_compliance_reportparameters are documented in the description but not in the schema: cbe_number, check_id, country, domain, entity_name, iban and 4 more
- noteTC11get_risk_scoreparameters are documented in the description but not in the schema: country, entity_name
- noteTC11get_trust_scorea parameter is documented in the description but not in the schema: entity_id
- noteTC11sanctions_previewparameters are documented in the description but not in the schema: country, name
- noteTC11sanctions_screenparameters are documented in the description but not in the schema: country, name
- noteTC11verify_leadparameters are documented in the description but not in the schema: address, company_number, country, domain, email, iban and 5 more
- noteTC11verify_walletparameters are documented in the description but not in the schema: chain_id, wallet_address
- noteTC29serverabout 385 tokens (10% of the definitions) are titles that repeat property or function names
The checks from /check and anchor check, run each day on the list above: about 3,516 tokens of definitions. Not part of the score yet. Check your own server.