generated: '2026-07-19'
method: searched
status: published
source: https://docs.judgmentlabs.ai/documentation/mcp-server
server:
  name: judgment
  transport: http
  url: https://mcp.judgmentlabs.ai
  auth: bearer
  auth_probe: HTTP 401 (authentication required) at https://mcp.judgmentlabs.ai
docs: https://docs.judgmentlabs.ai/documentation/mcp-server
plugin_repo: https://github.com/JudgmentLabs/judgment-plugin
config_example: "{\n  \"mcpServers\": {\n    \"judgment\": {\n      \"type\": \"http\",\n      \"url\"\
  : \"https://mcp.judgmentlabs.ai\"\n    }\n  }\n}\n"
description: The Judgment MCP server exposes production agent data — traces, sessions, behaviors, judges,
  projects, views, datasets, prompts, and automations — to MCP-capable AI code editors and to the in-product
  Judgment Agent. The same toolset that powers the Judgment Agent inside the platform is available over
  the Model Context Protocol.
tool_domains:
- traces
- sessions
- behaviors
- judges
- projects
- views
- datasets
- prompts
- automations
- agent-threads
- documentation
- organizations
deployment:
  mode: remote
  endpoint: https://mcp.judgmentlabs.ai
  verified: probed
  probe: gated
  checked: '2026-09-11'
  source: wall re-adjudication 2026-09-11 (RFC 9728 / JSON-RPC envelope)
  probe_prior: wall
  probe_why: RFC 9728 challenge (host-wide OAuth-protected resource)