api.limitguard.ai

Item: api.limitguard.ai
Rating: 86
Author: wmcp.sh

https://api.limitguard.ai/mcp

86/100 · MCP Trust Grade · checked 5h ago · MCP 2025-06-18

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 5 tools · Finance & Crypto

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 recommen

check_agent

Verify AI agent trust via LimitGuard. Checks if an AI agent is trusted based on its identifier. Used for multi-agent systems to verify delegation targ

get_trust_score

Quick trust score lookup by entity ID. Fast lookup for previously checked entities. Returns cached score if available. Args: entity_id: Entity identif

verify_wallet

Check wallet trust score for crypto payments. Verifies wallet against scam lists and transaction patterns. Supports EVM (0x...) and Solana (base58) ad

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:

Spec conformance20%80

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✗ unknown method → -32602
✓ tools/list → 5 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

5 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 3052ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%100

100% of tools have typed inputSchema
5/5 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade api.limitguard.ai on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — api.limitguard.ai grade B

Share on X Open card image

https://wmcp.sh/mcp/grade/api.limitguard.ai

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/api.limitguard.ai/badge.svg)](https://wmcp.sh/mcp/grade/api.limitguard.ai)

HTML

<a href="https://wmcp.sh/mcp/grade/api.limitguard.ai"><img src="https://wmcp.sh/mcp/grade/api.limitguard.ai/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.