MCP.Market

KnowJudges MCP server

online · 100% uptime
by knowjudges.com·com.knowjudges/knowjudges·v0.10.15
No reviews yet

Source-linked research on U.S. judges, courts, cases, and judicial analytics.

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed KnowJudges yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

KnowJudges tools (11)

write = sends, deletes, buys or posts
  • compare_immigration_analyticsFree

    Compare highest/lowest recorded immigration rates by judge or court, jointly filtered by state, nationality and calendar/fiscal proceeding-completion year. Defaults to asylum_denial_rate and minimum_decisions 1; a larger minimum is optional. Include small samples with decision counts and labels. Asylum percentages use grants plus denials, with procedural outcomes separate. At most ten results. Use proceeding_removal_rate only for explicitly requested broader proceeding outcomes. Historical rates do not predict individual outcomes or imply a choice of judge.

  • find_ai_abuse_casesFree

    Find reported AI-related legal-error cases, including fabricated citations and authorities. Use query for a case name, error type, or outcome; response distinguishes sanctions from no sanctions. Optional court, judge, state, and date filters narrow results. Returns at most 10 cases with verified decision links or labeled source fallbacks. Describe recorded allegations and outcomes; dataset inclusion alone does not establish a judicial finding of AI use. Empty and bulk searches are unavailable.

  • find_courtFree

    Find a court by name or location when the user asks for court identity, metadata, or a judge roster and its KnowJudges identity is unknown. For a named judge's courtroom presentation or practice rules, use get_courtroom_presentation_rules. Optionally narrow by jurisdiction or state. Returns at most 10 courts with names, state/jurisdiction, and canonical public URLs. No pagination or bulk listing is available. Use the returned court_url with get_court.

  • find_judgesFree

    Find likely US judges by identifying search text, optionally narrowed by court, state, or county. Use this before requesting a profile when the canonical KnowJudges profile URL is unknown. Specifically named matches may have historical or uncertain service; retain their reported status. Returns at most 10 matches linked to canonical KnowJudges profiles; empty and bulk searches are unavailable.

  • get_courtFree

    Get one court's identity, jurisdiction, profile URL, core metadata, and up to 10 judges classified as current when the user asks for court information or a roster. For a named judge's courtroom presentation or practice rules, use get_courtroom_presentation_rules. Use the court_url from find_court. Counts cover indexed profiles classified as active, senior, recalled, or visiting, not an independently verified complete bench. Retain roster coverage and location-specific contact notes. No pagination is available. An empty roster means no indexed current matches; a null count means unavailable roster data.

  • get_courtroom_presentation_rulesFree

    Answer a named judge's courtroom presentation or practice rules question using documented findings and source links. Resolve judge_url with find_judges. Use up to 10 topics to focus on materials, procedures, or a named part. Put relevant judge-specific requirements first and retain source deadlines. Summary Jury Trial and Commercial Division guidance is conditional. Broader rules are not personal preferences. Missing findings establish neither permission nor prohibition. Answer without looking up court metadata or a judge roster unless the user asks.

  • get_directory_countsFree

    Canonical Core counts for Judges, Courts and Courthouses, plus public biography, courtroom-rule and analytics coverage with category counts and snapshot date.

  • get_immigration_analyticsFree

    Get immigration judge or court outcomes using its canonical public profile URL. Filter jointly by nationality, calendar/fiscal proceeding-completion year and recorded court state. Asylum grant/denial percentages use grant-coded plus denied outcomes; procedural outcomes are separate. Samples below 35 decisions are labeled; no decisions means no rate. Returns sources and coverage. Use proceeding_removal_rate only for explicitly requested broader proceeding outcomes.

  • get_judge_biographyFree

    Get one judge's source-attributed birth details, education, and professional and judicial careers using the canonical profile URL from find_judges. Use for biographical questions rather than courtroom practice. Preserves date granularity, provenance, and source check dates; age is returned only for a valid full date of birth, otherwise null. Missing biography fields mean unavailable information, not a failed lookup.

  • get_judge_profileFree

    Get one judge's public profile using the canonical profile URL from find_judges. Use for identity and assignments; use get_judge_biography for biography and get_courtroom_presentation_rules for practice. Preserve stated uncertainty: an assignment end date does not by itself end judicial service or establish a senior-status transition. Source check dates describe evidence checks; last_updated describes publication. Missing fields are unavailable information. Broader rules are not personal preferences.

  • get_recent_rule_changesFree

    Find recorded KnowJudges profile or courtroom-rule changes since an inclusive date, optionally narrowed to the canonical judge_url from find_judges or court_url from find_court. Court filtering includes changes associated with that court and its indexed judge profiles; ambiguous court-only records are omitted. Use to check documented updates; returns at most 25 records. Change tracking begins at the reported launch date, so an empty result does not prove that no earlier real-world rule changed.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 3905ms17/20
  • Tool poisoning11 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 22 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How KnowJudges compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
11
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
905 ms
faster than 13% of 30,031 servers

What its tools let an agent do: 11 read

Install KnowJudges in Claude Code, Cursor or VS Code

claude mcp add --transport http knowjudges https://mcp.knowjudges.com/mcp
Add to Cursor

What the publisher says

From the KnowJudges repository's README, as published. We do not edit it. Read it on GitHub

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.

getjudgeprofile

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

getjudgebiography

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

getcourtroompresentation_rules

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

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

findaiabuse_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

getrecentrule_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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

KnowJudges: common questions

Is KnowJudges MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the KnowJudges safety report
How do I install KnowJudges?
It runs remotely at mcp.knowjudges.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does KnowJudges need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is KnowJudges maintained?
The last commit was 23 days ago (2026-10-12). The latest release is v0.10.15.
Is KnowJudges up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does KnowJudges compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.