Know Your Judge MCP
Add judge research tools directly to an AI assistant.
The remote MCP server exposes four focused tools over Streamable HTTP. Compatible AI clients can discover the tools, validate their inputs, and receive structured, source-linked KYJ results without a custom integration layer.
Shared public allowance
Built for focused research, not bulk extraction
API and MCP requests share one allowance for each public client or network. A request blocked by either window returns HTTP 429.
- Hourly
- 20 requests
- Daily
- 100 requests
Need a dataset, recurring feed, or higher-volume access? Contact us about bulk data access.
Connect
For AI clients with remote MCP support
- Open the client's connectors, integrations, or MCP settings.
- Add a custom remote MCP server.
- Enter
https://mcp.knowjudges.com/mcp and choose Streamable HTTP if the client asks for a transport. - No authorization header is required for public access.
- Enable the discovered KYJ tools, then run the test prompt below.
{
"mcpServers": {
"know-your-judge": {
"url": "https://mcp.knowjudges.com/mcp"
}
}
}
Configuration field names vary by AI product. If your client asks only for a server URL, use the URL above rather than the full JSON example.
Available tools
What the AI can call
find_judgesResolve a likely judge and canonical KYJ slug.get_judge_profileRetrieve a public profile with sources and scoped findings.get_courtroom_presentation_rulesFocus on PowerPoint, video, exhibits, demonstratives, and related topics.get_recent_rule_changesRead changes recorded after KYJ change tracking began.
Verify
Use a provenance-aware test prompt
Find Judge James Boasberg, then return any courtroom presentation rules with the scope and source URL for each finding.
A good response identifies whether a finding is judge-specific, courtroom, courtwide, or statewide and links the public source. Silence in a public source is not evidence that a technology is permitted or prohibited.
Request accounting
Plan for more than one MCP request
MCP initialization, tool discovery, and individual tool calls are separate HTTP requests. They all draw from the shared public allowance, as do REST API requests from the same client or network.
For production agents, batch research, or a private integration, please contact SwansLake about bulk access.