KnowJudges MCP

Add source-linked U.S. judge and court research directly to AI assistants and agents through the Model Context Protocol.

Website: https://knowjudges.com MCP documentation: https://knowjudges.com/mcp Remote MCP endpoint: https://mcp.knowjudges.com/mcp

Overview

The KnowJudges MCP server exposes six focused research tools over Streamable HTTP.

Compatible MCP clients can discover the available tools, validate inputs, and retrieve structured, source-linked KnowJudges results without building a custom API integration.

Public access currently requires no authentication token.

Connect

Use this remote MCP endpoint:

https://mcp.knowjudges.com/mcp

Transport: Streamable HTTP Authentication: None required for public access

For clients that support an MCP server configuration object:

{
  "mcpServers": {
    "know-your-judge": {
      "url": "https://mcp.knowjudges.com/mcp"
    }
  }
}

Configuration field names vary between MCP clients. If your client asks only for a server URL, enter:

https://mcp.knowjudges.com/mcp

The official KnowJudges connection instructions use this same remote endpoint and transport.

Available tools

find_judges

Resolve a likely judge and canonical KnowJudges slug.

Use this when you know some combination of a judge's name, court, or jurisdiction and need to identify the correct KnowJudges profile.

get_judge_profile

Retrieve a public judge profile containing source-linked, scoped findings.

get_judge_biography

Retrieve sourced public background information about a judge without behavioral inference.

get_courtroom_presentation_rules

Research courtroom presentation requirements and guidance, including topics such as:

• PowerPoint
• Video
• Exhibits
• Demonstratives
• Related courtroom presentation requirements

find_ai_abuse_cases

Find up to 10 court cases involving AI-generated legal errors.

Results can include:

• Judge
• Court response
• Dataset source
• Verified official decision link when available

get_recent_rule_changes

Retrieve changes recorded since KnowJudges change tracking began.

These are the six tools currently exposed by the public MCP service.

Example prompt

After connecting the MCP server, try:

Find the five most recent New York court cases involving fabricated AI-generated legal material. Include the judge, court response, and verified official decision URL when available.

A provenance-aware response should preserve the underlying source information and avoid making claims beyond what the published records support.

Rate limits

The public KnowJudges REST API and MCP server share the same allowance for each public client or network:

Requests exceeding either limit return HTTP 429.

MCP initialization, tool discovery, and individual tool calls are separate HTTP requests and each counts toward this shared allowance.

For datasets, recurring feeds, batch research, higher-volume usage, or private integrations, see:

https://knowjudges.com/mcp

Provenance

KnowJudges is designed around source-linked research.

Applications and agents should preserve source information returned by MCP tools, including official decision links and other provenance metadata where available.

In particular:

• Do not remove source URLs when presenting results.
• Do not represent a source as supporting more than it actually states.
• Distinguish judge-specific information from courtwide or jurisdiction-wide guidance.
• Preserve verified official decision links when returned.
• Do not convert sourced facts into unsupported behavioral conclusions.

Example research workflow

A typical agent workflow might be:

User question
    ↓
find_judges
    ↓
canonical judge
    ↓
get_judge_profile
    ↓
get_judge_biography
    ↓
get_courtroom_presentation_rules
    ↓
source-linked answer

For legal-AI research:

User question
    ↓
find_ai_abuse_cases
    ↓
source-linked cases
    ↓
verified official decisions where available

REST API

KnowJudges also provides a public REST API for applications that do not use MCP.

API documentation:

https://knowjudges.com/api

MCP is generally the simpler interface for MCP-compatible AI assistants and agents, while the REST API provides direct HTTP access for conventional applications.

Links

• KnowJudges: https://knowjudges.com
• Judicial Registry: https://knowjudges.com/kyj
• Judicial Directory: https://knowjudges.com/judicial-directory
• API: https://knowjudges.com/api
• MCP documentation: https://knowjudges.com/mcp
• Remote MCP endpoint: https://mcp.knowjudges.com/mcp

About KnowJudges

KnowJudges provides free, source-linked research on U.S. judges and courts through public judicial profiles, court information, research tools, API access, and MCP integrations.

The MCP server is intended to make that information directly usable by AI assistants, research agents, and other MCP-compatible software while preserving the provenance of the underlying research.

For current terms, data-use information, licensing information, and corrections policies, refer to the relevant pages on https://knowjudges.com.