com.bonissystems/trustai-verify

MCPcommunitylive
v1.0.0com.bonissystemsUnknownUpdated 3mo ago

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

Endpoint healthlive
checked 10 days ago · 427ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorcom.bonissystems
LicenseUnknown
Version1.0.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface4 tools · none privileged
Security scan✓ Cleanvlive · 28d agoHow well does this scan work?
EvalsNone
IndexedJun 25, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Observed live from the vendor's endpoint28d ago

Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.

  • https://trustailaw.com/api/mcp4 tools · 457ms
get_descriptorReturn 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.

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.

No input schema was published for this tool.

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

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

No input schema was published for this tool.

get_healthReturn 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.

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.

No input schema was published for this tool.

review_legal_textIndependently 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 e…

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 e…

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

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.