verdict_contract — SCRIPTMASTERLABS — Verdict Protocol MCP Tool
verdict_contract
(verdict contract) is one of 6 tools on the
SCRIPTMASTERLABS — Verdict Protocol
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verdict_contract from your client
- Claude Code SCRIPTMASTERLABS — Verdict Protocol verdict_contract run in your project directory
- Claude Desktop SCRIPTMASTERLABS — Verdict Protocol verdict_contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SCRIPTMASTERLABS — Verdict Protocol verdict_contract ~/.cursor/mcp.json
- VS Code SCRIPTMASTERLABS — Verdict Protocol verdict_contract .vscode/mcp.json
- Zed SCRIPTMASTERLABS — Verdict Protocol verdict_contract ~/.config/zed/settings.json
- Windsurf SCRIPTMASTERLABS — Verdict Protocol verdict_contract ~/.codeium/windsurf/mcp_config.json
- Cline SCRIPTMASTERLABS — Verdict Protocol verdict_contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SCRIPTMASTERLABS — Verdict Protocol verdict_contract ~/.gemini/settings.json
- Grok SCRIPTMASTERLABS — Verdict Protocol verdict_contract .mcp.json (in your project root)
- ChatGPT SCRIPTMASTERLABS — Verdict Protocol verdict_contract Settings → Connectors → Advanced → Developer mode
- Claude.ai SCRIPTMASTERLABS — Verdict Protocol verdict_contract Settings → Connectors → Add custom connector
- LangChain SCRIPTMASTERLABS — Verdict Protocol verdict_contract pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http verdict https://verdict.scriptmasterlabs.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 26 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.