TrustAI Verification
REMOTE · TRUSTAILAW.COM · SCANNED SEP 24
Neutral referee for legal-AI output: flags orphan quotes and uncited claims. Not legal advice.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 387 tokens (~96/item across 4 items; 4 tools + 0 resources), lean.Pass
- 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
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
claude mcp add --transport http com-bonissystems-trustai-verify 'https://trustailaw.com/api/mcp'
{
"mcpServers": {
"com-bonissystems-trustai-verify": {
"url": "https://trustailaw.com/api/mcp"
}
}
} {
"servers": {
"com-bonissystems-trustai-verify": {
"type": "http",
"url": "https://trustailaw.com/api/mcp"
}
}
} [mcp_servers.com-bonissystems-trustai-verify] url = "https://trustailaw.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-bonissystems-trustai-verify": {
"type": "remote",
"url": "https://trustailaw.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-bonissystems-trustai-verify --url 'https://trustailaw.com/api/mcp' --transport streamable-http
mcp_servers:
com-bonissystems-trustai-verify:
url: "https://trustailaw.com/api/mcp" {
"McpServers": {
"com-bonissystems-trustai-verify": {
"Transport": "http",
"Url": "https://trustailaw.com/api/mcp"
}
}
} assistant mcp add com-bonissystems-trustai-verify -t streamable-http -u 'https://trustailaw.com/api/mcp'
{
"mcpServers": {
"com-bonissystems-trustai-verify": {
"type": "http",
"url": "https://trustailaw.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 −6
- Stability: pass → 0.63 functional
- 4 Sept 26 +45
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
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 24 Sept 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=YE2,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5c9c4e45595155c750bb734f0560ba2f118 |
| SANs: *.trustailaw.com, trustailaw.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | present | 19718 | 13 | Verified |
| trustailaw.com. | absent | 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 |
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 →
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 ~202
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.)
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The legal text to review (a memo, brief, or answer from any AI vendor). Max 200000 chars. |
No output schema declared.
No examples provided.
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 80 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 329 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.