mcpbeat Sign in

TrustAI Verification MCP Server

answering

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

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

Uptime history 91 days of history · worst day 87%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
583 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.

15 Oct a tool description was rewritten review_legal_text

TrustAI Verification missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add trustai-verify --transport http https://trustailaw.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "trustai-verify": {
      "type": "http",
      "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, the citation sentence after it, or its footnote; (2) uncited propositions — law stated as established (a holding cue or a settled-law phrase such as 'it is well established') with no such citation; (3) court mismatch — the text names one circuit, the cite another; (4) impossible date — a citation year in the future or before its reporter series began; (5) court/reporter mismatch — a court and reporter that cannot both be right; (6) a case name and cite matching one publicly identified as non-existent in Mata v. Avianca (S.D.N.Y. 2023). Recognizes full and short-form cites (Id., supra, Westlaw/Lexis, U.S.C., C.F.R., state codes, court rules) and footnotes; triggers in English and Spanish. Returns each flag with the exact passage, its offsets, a severity 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 313 ms 9 min ago

Alternatives to TrustAI Verification

same job, measured the same way
Diaspora MCP
by gabrielmahia

Guides for Kenyans abroad: citizenship, taxes, investment, document verification. Not legal advice.

255 installs/wk local only
Human For AI
by humanforai

Hire a real human for real-world verification, product testing, AI output review, and errands.

51 installs/wk 6 tools answering
Policy Pal
by policypal

Grounded, quoted readings of privacy policies and terms of service. Not legal advice.

3 tools answering
Verirun
by baopeak

Execution-grounded verification for AI coding agents on Windows: evidence, not agent claims.

33 installs/wk local only
R
R/IV — Verify Claims, Citations & Agent Actions
by duranivrobert-glitch

Verify claims, citations & agent actions. Free receipt trial; paid prices via live R/IV quotes.

35 tools answering
Cicadas local MCP
by kevinwowo

Local Cicadas MCP for models, quotes and status. Authenticated API flows not yet verified.

local only
asms
by asms

Phone numbers for AI agents: SMS verification codes and rented numbers that receive SMS.

12 tools answering
referencesource.org
by joelp22-maker

Verified reference data; each record carries its source URL and quote. verify_quote checks claims.

50 installs/wk 8 tools answering

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 583 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 in the form 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 583 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.