Categories › AI & Agents › Thinking, planning & prompt tools
Verdict Protocol MCP: five-juror Jev decisions. Seal settle-proven 2026-11-02 (SELF-PROOF).
Remote server: your requests and data go to verdict.scriptmasterlabs.com. Claude Code: claude mcp add --transport http scriptmasterlabs-verdict-protocol https://verdict.scriptmasterlabs.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
verdict_status — Read current readiness and decision-only service identity. Configuration readiness is not proof of a fresh Jev evaluation or settlement. No verdict_contract — Read the live Verdict Protocol OpenAPI contract and separate paid HTTP service requirements. This tool never calls /decide or /seal and cannverdict_compile_capsule — Freeze caller-supplied research state into a timestamped SHA256 capsule using the production compiler. Stateless: no persistence, Jev call, verdict_verify_capsule — Recompute the hash of a supplied frozen capsule. A matching hash proves internal integrity only, not source truth, SML issuance, receipt autverdict_review_jury — Validate five uniquely identified caller-supplied juror votes and recompute the production jury aggregation. No new Jev evaluation occurs. Tverdict_decide — Invoke the existing /decide service: five Jev jurors over a frozen capsule, with persisted signed receipt. Without payment returns the freshNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.