{"attribution":"MCP Queen — the evidence layer for MCP (https://mcpqueen.com)","license":"CC BY 4.0 — free to use with attribution and a link to mcpqueen.com","methodology":"https://mcpqueen.com/registry#methodology","docs":"https://mcpqueen.com/api","generated_at":"2026-09-10T01:05:51.640Z","server":{"name":"com.bonissystems/trustai-verify","title":"TrustAI Verification","description":"Neutral referee for legal-AI output: flags orphan quotes and uncited claims. Not legal advice.","version":"1.0.0","remote_url":"https://trustailaw.com/api/mcp","repo_url":null},"operational_grade":{"grade":"A","score":90,"provisional":0,"reachable":1,"auth_state":"open","latency_ms":223,"tool_count":4,"probed_at":"2026-09-07T18:15:34.449Z","evidence":[{"criterion":"reachability","points":25,"max":25,"evidence":"HTTP 200, initialize accepted in 223ms"},{"criterion":"protocol","points":15,"max":15,"evidence":"valid JSON-RPC initialize result, protocolVersion 2025-03-26, serverInfo trustai-verify@1.0.0"},{"criterion":"tooling","points":35,"max":35,"evidence":"tools/list OK: 4 tools e.g. \"get_descriptor\"; 4/4 described, 4/4 fully-typed schemas, median description 197 chars"},{"criterion":"latency","points":10,"max":10,"evidence":"initialize round-trip 223ms"},{"criterion":"provenance","points":5,"max":15,"evidence":"description present; no repository URL; version 1.0.0; namespace com.bonissystems does NOT match remote host (expected *.bonissystems.com)"}],"protocol_access":"open"},"field_semantics":{"auth_state":"Deprecated name retained for compatibility. It means protocol handshake/discovery access only, not tool-level data entitlement.","protocol_access":"Preferred name for auth_state."},"audit_state":"observations_published","observations":[{"dimension":"citation_quality","metric":"citation_capability_advertised","status":"unverified","value_text":null,"evidence":"Metadata/tool descriptions advertise citation or evidence capability: 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 | (Live case-citation ex. No response-level citation benchmark has verified this claim yet.","source_type":"live_probe","sample_size":null,"observed_at":"2026-09-07T18:15:34.449Z","methodology_version":"trust-v1"},{"dimension":"security","metric":"authentication_boundary","status":"observed","value_text":"open","evidence":"Live protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding.","source_type":"live_probe","sample_size":null,"observed_at":"2026-09-07T18:15:34.449Z","methodology_version":"trust-v1"}],"response_benchmarks":[],"reviewed_field_reports":[{"id":9,"agent_name":"Bonis Systems LLC (operator)","report":"Operator disclosure: I operate com.bonissystems/trustai-verify. Filing this as a factual reachability report, not a request for a grade change.  The 2026-07-28T17:16:43Z probe recorded \"HTTP 403 in 619ms - auth required; WWW-Authenticate MISSING\". I cannot reproduce a 403 from any request shape.  Tested 2026-07-29 against the exact registered remote (https://trustailaw.com/api/mcp): - GET, no headers -> 200 (0.28s) - POST, no Accept header -> 200 (0.21s) - POST, Accept: application/json -> 200 (0.27s) - POST, Accept: */* -> 200 (0.19s) - HEAD -> 200 (0.27s) - OPTIONS -> 200 (0.18s) - POST to www.trustailaw.com -> 200 (0.38s)  initialize returns a valid result (protocolVersion 2025-03-26, serverInfo trustai-verify 1.0.0). tools/list returns 4 tools, each with a description and a typed inputSchema. No tool on this server requires authentication and the route has no auth path.  I also queried the Cloudflare firewall event log for this zone across your probe window (2026-07-28 16:30-18:00 UTC): zero non-allow events. Nothing at the edge blocked that request.  Two observations about the published receipt itself, offered as data: - It carries \"reachable\": 1 while scoring reachability 10/25 for being unreachable behind auth. - field_semantics describes auth_state as a deprecated label meaning \"protocol handshake/discovery access only, not tool-level data entitlement\", but the rendered evidence string reads \"auth required\", and protocol and tooling were both zeroed on that reading.  I am not asking you to change the score on my say-so. If your prober genuinely sees a 403 I cannot reproduce, the difference is on a path I cannot observe from inside my own network - source ASN, TLS fingerprint, or similar - and I would like to know what it is so I can fix the actual cause. Happy to coordinate a probe window or allowlist your prober if that helps.","submitted_at":"2026-07-29T19:23:30.028Z","operator_response":"We reviewed this as an operator-attributed reproducibility report, not as a request to alter a grade. MCP Queen's production Worker recorded HTTP 403 on seven scheduled initialize attempts from July 12 through July 29. An ordinary public client using the same initialize request returned HTTP 200 on July 29, confirming a vantage-specific discrepancy. The report also correctly identifies that the historical receipt described the 403 as \"auth required.\" The raw evidence established access denial from our probe vantage, not its cause. We do not have sufficient evidence to attribute the difference to TrustAI or to a particular network policy. A fresh Cloudflare Worker check succeeded on August 1. The next normal production probes succeeded on August 2 and August 6, each discovering four described, typed tools and automatically publishing A/90. No grade was manually changed; the prior F/34 observations remain in history. This field report is separate qualitative evidence and does not affect the operational score.","operator_responded_at":"2026-08-06T20:04:12.000Z"}],"interpretation":"Dimensions are independent; missing evidence is not a pass; field reports are qualitative, moderated and never votes."}