Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TrustAI Verification

REMOTE · TRUSTAILAW.COM

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

Available components

0 this week 86 Trust /100

Last scanned (22 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 524 tokens (~131/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 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
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 15 Nov 26 0
    • Tool “review_legal_text” rewrote its description, which is the text the model reads security
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Oct 26 0
    • Tool “review_legal_text” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
  • 15 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • Tool “get_descriptor” changed its title: About this server cosmetic
    • Tool “get_health” changed its title: Server health cosmetic
    • Tool “list_checks” changed its title: What it checks, and never claims cosmetic
    • Tool “review_legal_text” changed its title: Review legal text for unsupported quotes and claims cosmetic
  • 4 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://trustailaw.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trustailaw.com CN=YE1,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA384 6aac1cbb3325595a1cb1ce7e3e3bb094b76
SANs: *.trustailaw.com, trustailaw.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of trustailaw.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
trustailaw.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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; preload
x-content-type-options nosniff
x-frame-options DENY

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://trustailaw.com/api/mcp Verified 200
http (plaintext) http://trustailaw.com/api/mcp HTTPS enforced 302 https://trustailaw.com/api/mcp
MCP tools · 4 exposed · ~466 tokens

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 →

Tool Tokens
get_descriptor ~46

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_health ~45

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_checks ~36

Return the structural checks this server performs on legal-AI output, and — explicitly — what it never claims. Information, not legal advice.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

review_legal_text ~339

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. It does not check whether a cited case exists, and it does not compare the answers of several AI models.

NameTypeReqDescription
textstringyesThe legal text to review (a memo, brief, or answer from any AI vendor). Max 200000 chars.

No output schema declared.

No examples provided.

Install

How do I install the TrustAI Verification MCP server?

TrustAI Verification is a hosted endpoint at https://trustailaw.com/api/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 · trustailaw.com

# add to Claude Code
claude mcp add --transport http com-bonissystems-trustai-verify 'https://trustailaw.com/api/mcp'
Common questions

What is the TrustAI Verification MCP server?

TrustAI Verification is an MCP server listed in the public MCP registry as com.bonissystems/trustai-verify. Neutral referee for legal-AI output: flags orphan quotes and uncited claims. Not legal advice. This page covers its hosted endpoint (https://trustailaw.com/api/mcp).

Is the TrustAI Verification MCP server safe to use?

TrustAI Verification scores 86 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 TrustAI Verification MCP server expose?

TrustAI Verification exposes 4 tools: get_descriptor, list_checks, get_health, review_legal_text. Their descriptions and schemas cost roughly 466 tokens of context every time the server is loaded.

Does the TrustAI Verification MCP server require authentication?

No. We connected to TrustAI Verification without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TrustAI Verification MCP server still maintained?

TrustAI Verification is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the TrustAI Verification MCP server?

VerifyMCP ran 13 checks on TrustAI Verification, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.