SCRIPTMASTERLABS — Verdict Protocol
REMOTE · VERDICT.SCRIPTMASTERLABS.COM
Verdict Protocol MCP: five-juror Jev decisions. Seal settle-proven 2026-11-02 (SELF-PROOF).
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 495 tokens (~82/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Tool “verdict_contract” rewrote its description, which is the text the model reads security
- Tool “verdict_decide” rewrote its description, which is the text the model reads security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 66
First indexed and scored.
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 5 Nov 2026 · Probed https://verdict.scriptmasterlabs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verdict.scriptmasterlabs.com | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8a9e722de26a1560ecbc728cc5064e6 |
| SANs: verdict.scriptmasterlabs.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verdict.scriptmasterlabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| scriptmasterlabs.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verdict.scriptmasterlabs.com/mcp | Verified | 200 | |
| http (plaintext) | http://verdict.scriptmasterlabs.com/mcp | HTTPS enforced | 301 | https://verdict.scriptmasterlabs.com/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 →
verdict_compile_capsule Compile a decision capsule ~61
Freeze caller-supplied research state into a timestamped SHA256 capsule using the production compiler. Stateless: no persistence, Jev call, signature, paid receipt, trade approval or settlement. The timestamp changes each compilation.
| Name | Type | Req | Description |
|---|---|---|---|
| capsule | object | yes | – |
No output schema declared.
No examples provided.
verdict_contract Verdict API contract ~71
Read the live Verdict Protocol OpenAPI contract and separate paid HTTP service requirements. This tool never calls /decide or /seal and cannot authorize payments or forward keys. Paid HTTP tiers: /decide is $0.25 USDC and /seal is $0.01 USDC via x402 on Base.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verdict_decide Run paid BYOK Jev verdict ~129
Invoke the existing /decide service: five Jev jurors over a frozen capsule, with persisted signed receipt. Without payment returns the fresh x402 challenge. Requires caller Jev key in X-JEV-API-KEY and a caller-created PAYMENT-SIGNATURE header or payment_signature argument. Never creates a wallet signature or submits trades. model_spend_authorized=true is required before paid execution. Paid: $0.25 USDC via x402 on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| capsule | object | yes | – |
| model_spend_authorized | boolean | – | – |
| payment_signature | string | – | – |
No output schema declared.
No examples provided.
verdict_review_jury Review supplied Jev jury votes ~72
Validate five uniquely identified caller-supplied juror votes and recompute the production jury aggregation. No new Jev evaluation occurs. The report is untrusted input: aggregation does not authenticate issuance, correctness, independence, trade approval or payment.
| Name | Type | Req | Description |
|---|---|---|---|
| capsule | object | yes | – |
| votes | array | yes | – |
No output schema declared.
No examples provided.
verdict_status Verdict runtime status ~39
Read current readiness and decision-only service identity. Configuration readiness is not proof of a fresh Jev evaluation or settlement. No model, wallet or trade call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verdict_verify_capsule Check capsule hash integrity ~58
Recompute the hash of a supplied frozen capsule. A matching hash proves internal integrity only, not source truth, SML issuance, receipt authenticity, Jev execution or payment. No model or wallet call.
| Name | Type | Req | Description |
|---|---|---|---|
| capsule | object | yes | – |
No output schema declared.
No examples provided.
How do I install the SCRIPTMASTERLABS — Verdict Protocol MCP server?
SCRIPTMASTERLABS — Verdict Protocol is a hosted endpoint at https://verdict.scriptmasterlabs.com/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 · verdict.scriptmasterlabs.com
claude mcp add --transport http com-scriptmasterlabs-verdict 'https://verdict.scriptmasterlabs.com/mcp'
What is the SCRIPTMASTERLABS — Verdict Protocol MCP server?
SCRIPTMASTERLABS — Verdict Protocol is an MCP server listed in the public MCP registry as com.scriptmasterlabs/verdict. Verdict Protocol MCP: five-juror Jev decisions. Seal settle-proven 2026-11-02 (SELF-PROOF). This page covers its hosted endpoint (https://verdict.scriptmasterlabs.com/mcp).
Is the SCRIPTMASTERLABS — Verdict Protocol MCP server safe to use?
SCRIPTMASTERLABS — Verdict Protocol scores 71 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 SCRIPTMASTERLABS — Verdict Protocol MCP server expose?
SCRIPTMASTERLABS — Verdict Protocol exposes 6 tools: verdict_status, verdict_contract, verdict_compile_capsule, verdict_verify_capsule, verdict_review_jury, verdict_decide. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.
Does the SCRIPTMASTERLABS — Verdict Protocol MCP server require authentication?
No. We connected to SCRIPTMASTERLABS — Verdict Protocol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SCRIPTMASTERLABS — Verdict Protocol MCP server still maintained?
SCRIPTMASTERLABS — Verdict Protocol is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.