The evidence layer
you don’t have to build.
Claude for Legal ships accuracy — citation attribution, conservative privilege defaults. It does not ship cryptographic sealing, chain of custody, transparency-log anchoring, or FRE 902(14) authentication packets. Verdict is that layer: the cryptographic substrate underneath the output.
It extends your surface. It is not a competitor to Claude, to CoCounsel, or to any connector in the directory. Workflow stays yours. Verdict adds the record.
Don’t take our word.
Seal something.
verdict.systems/live-seal takes any sentence, produces a real Sealed Evidence Record, and anchors its Merkle root to the public Sigstore Rekor transparency log — the same code path the production verdict_create_evidence_record MCP tool runs. You get a clickable Rekor URL you can verify without trusting us. No account, no install, under five seconds.
A replay of the real /live-seal flow, ending on a genuine Sigstore Rekor entry minted 2026-05-15. Run it yourself →
The proposed Federal Rule of Evidence 707 extends Daubert-style reliability scrutiny to machine-generated output offered without an expert. A Claude legal output with no sealed provenance is the exact artifact that rule targets. Verdict produces the record that survives it.
Florida, California, New Jersey and others now impose competence and disclosure duties for generative AI in legal work. The defensible answer to 'what did the model produce, when, and was it reviewed' is a sealed record — not a screenshot.
Article 12 requires automatic, tamper-evident logging over the lifetime of a high-risk AI system. Verdict's Sealed Evidence Record + Sigstore Rekor anchor is that log, independently verifiable without trusting the vendor.
The same call, from Claude.
JSON-RPC 2.0 / MCP protocol 2025-06-18. Apache 2.0. The remote endpoint is the same surface every Claude for Legal plugin can reference from its .mcp.json.
# Remote endpoint — live Sigstore Rekor anchoring on every record
claude mcp add verdict --transport http --url https://verdict.systems/api/mcp
# Local stdio — offline-capable
claude mcp add verdict-local -- npx -y @verdict-systems/mcpFull install guide for Claude Code, Claude Cowork, and claude.ai →
The rules are arriving.
Directory connector
List @verdict-systems/mcp in the Claude connector directory as the independent evidence layer — the same surface every Claude for Legal plugin can reference from its .mcp.json.
Upstream PR
PR #20 on anthropics/claude-for-legal is open: Verdict as a connector across the six plugins most exposed to FRE 707 and state-bar disclosure — commercial, corporate, litigation, AI-governance, IP, regulatory.
Skill packaging
Verdict sealing as an installable skill under legal-builder-hub. Every contract reviewed, brief drafted, docket alert becomes one tool call from sealed.
Substrate, not rival
CoCounsel is workflow + research. Agentforce is orchestration. Verdict is the record underneath all of it. It underwrites the Claude surface; it does not compete with any part of it.
Verdict is not an Anthropic partner and is not an endorsed or directory-listed connector. An outreach packet has been sent to partnerships@anthropic.com and PR #20 is open for review. Three USPTO patent applications are filed (one non-provisional, two provisional). The Sealed Evidence Record format and Sigstore anchoring are Apache 2.0 and independently verifiable today. Nothing on this page should be read as a claim of partnership or endorsement until that is true and announced jointly.
You built the intelligence.
Verdict makes its output stand up in court.