mcpbeat

TrustAI Verification MCP Server

com.bonissystems/trustai-verify
answering

TrustAI Verification is answering right now. Last checked 3 min ago. It exposes 4 tools.

Neutral referee for legal-AI output: flags orphan quotes and uncited claims. Not legal advice.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
297 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 3 min ago.

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

checks
list_checks
Return the structural checks this server performs on legal-AI output, and — explicitly — what it never claims. Information, not legal advice.
descriptor
get_descriptor
Return the TrustAI Verification MCP self-description: operator, what the server verifies, the public tools, the boundary it never crosses (it never adjudicates), and links to the public surfaces.
health
get_health
Return server health: process uptime and a deterministic engine self-check (the structural detectors run on a fixed sample and return the expected flag counts). Local-only; no database on the path.
review
review_legal_text
Independently review legal text produced by ANY AI vendor for the structural red-flags behind fabrication risk: (1) orphan quotations — a quoted span with no citation in its sentence; (2) uncited propositions — a legal proposition stated as established with no citation. Returns each flag with the exact passage and a plain structural observation, FOR YOUR REVIEW. It is a neutral referee: it never tells you the answer is right or wrong, never adjudicates, and abstains (returns no flags) on any fault rather than fabricating one. Deterministic and local — no external lookup. (Live case-citation existence checking against CourtListener runs on the website verifier at /verify; multi-model cross-validation runs in TrustAI's document-analysis engine and the licensed pilot — neither runs on this load-safe tool.)

Endpoints

URLTransportStateLatencyChecked
https://trustailaw.com/api/mcp streamable-http answering 277 ms 3 min ago

TrustAI Verification — questions

Answers built from our own checks of this server.

What can TrustAI Verification do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_descriptor, get_health, list_checks, review_legal_text. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is TrustAI Verification working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 297 ms. The bar chart above shows every period we have measured.
How do I connect TrustAI Verification?
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 TrustAI Verification need an API key?
No. TrustAI Verification completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is TrustAI Verification?
It answers our handshake in 297 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.