KnowJudges
REMOTE · MCP.KNOWJUDGES.COM
Source-linked research on U.S. judges, courts, cases, and judicial analytics.
Available components
Last scanned (8 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1595 tokens (~145/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management75
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 5 additions. See how to fix → Fail
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 0
- Tool “get_directory_counts” rewrote its description, which is the text the model reads security
- Server version: 2.7.1 → 2.7.3 functional
- 25 Oct 26 0
- Server version: 2.4.0 → 2.7.1 functional
- 20 Oct 26 0
- Schema quality: excellent → good functional
- New tool “get_directory_counts” functional
- 13 Oct 26 0
- “find_court” reworded the description of “jurisdiction” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 10 Oct 26 +1
- Stability: pass → fail ▼ security
- Authorization: unverified → partial ▲ security
- Tool coverage: 95% → 58% ▼ functional
- Schema quality: pass → fail ▼ functional
- First check of Tool coverage: 100 functional
- Server version: 1.0.5 → 2.4.0 functional
- New tool “compare_immigration_analytics” functional
- New tool “get_immigration_analytics” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.knowjudges.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=knowjudges.com | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d2ed6b7c992d7c1a1332000e21307801 |
| SANs: knowjudges.com, mcp.knowjudges.com, *.mcp.knowjudges.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.knowjudges.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| knowjudges.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), geolocation=(), microphone=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.knowjudges.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.knowjudges.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_immigration_analytics ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| limit | integer | – | – |
| metric | string | – | – |
| minimum_decisions | integer | – | Minimum grant-or-denial decisions; defaults to 1. Samples below 35 are labeled, not hidden. |
| nationality | string | – | – |
| order | string | – | – |
| state | string | – | – |
| year | integer | – | – |
| year_basis | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | yes | – |
| denominator_definition | string | yes | – |
| eligible_entities | integer | yes | – |
| geography_definition | string | yes | – |
| limitations | array | yes | – |
| message | string | yes | – |
| metric | string | yes | – |
| minimum_decisions | integer | yes | – |
| nationality | – | yes | – |
| period | object | yes | – |
| results | array | yes | – |
| source | – | yes | – |
| state | – | yes | – |
No examples provided.
find_ai_abuse_cases ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | Court name fragment |
| from_date | string | – | Inclusive earliest decision date |
| judge | string | – | Judge name fragment |
| limit | integer | – | Maximum results, capped at 10 |
| query | string | – | Case name, error type, ruling text, court, state, or judge search text |
| response | string | – | Court response, for example Warning or Sanctions |
| state | string | – | US state name |
| to_date | string | – | Inclusive latest decision date |
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| limit | integer | yes | – |
| public_access | object | yes | – |
| results | array | yes | – |
| total_matches | integer | yes | – |
No examples provided.
find_court ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | – | Two-letter jurisdiction code. US means national courts such as the Supreme Court; geographically assigned federal courts use their state code, for example NY for SDNY. |
| limit | integer | – | – |
| query | string | yes | Court name or location search text |
| state | string | – | State name or postal abbreviation |
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| limit | integer | yes | – |
| programs | array | – | – |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
find_judges ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | County name fragment |
| court | string | – | Court name fragment |
| limit | integer | – | Maximum results, capped at 10 |
| query | string | yes | Judge name or other identifying search text |
| state | string | – | US state name or postal abbreviation, for example DC or California |
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| limit | integer | yes | – |
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
get_court ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| court_url | string | yes | Exact canonical court_url returned by find_court |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| court | object | yes | – |
| current_judge_count | – | yes | – |
| judges | array | yes | – |
| limit | integer | yes | – |
| roster_coverage | string | yes | – |
| roster_truncated | boolean | yes | – |
| texas_coverage | object | – | – |
No examples provided.
get_courtroom_presentation_rules ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| judge_url | string | yes | Canonical profile_url returned by find_judges |
| topics | array | – | Optional presentation topics to filter |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string | yes | – |
| findings | array | yes | – |
| judge | object | yes | – |
| requested_topics | array | yes | – |
| scope_note | – | – | – |
No examples provided.
get_directory_counts ~45
Canonical Core counts for Judges, Courts and Courthouses, plus public biography, courtroom-rule and analytics coverage with category counts and snapshot date.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | object | yes | – |
| coverageScope | string | yes | – |
| definitions | object | yes | – |
| generatedAt | string | yes | – |
| jurisdictions | array | yes | – |
| kind | string | yes | – |
| labels | object | yes | – |
| schemaVersion | number | yes | – |
| scopes | object | yes | – |
| source | string | yes | – |
| totals | object | yes | – |
No examples provided.
get_immigration_analytics ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | – |
| metric | string | – | – |
| nationality | string | – | – |
| profile_url | string | yes | – |
| state | string | – | – |
| year | integer | – | – |
| year_basis | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | yes | – |
| denominator_definition | string | yes | – |
| eligible_entities | integer | yes | – |
| geography_definition | string | yes | – |
| limitations | array | yes | – |
| message | string | yes | – |
| metric | string | yes | – |
| minimum_decisions | integer | yes | – |
| nationality | – | yes | – |
| period | object | yes | – |
| results | array | yes | – |
| source | – | yes | – |
| state | – | yes | – |
No examples provided.
get_judge_biography ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| judge_url | string | yes | Canonical profile_url returned by find_judges |
| Name | Type | Req | Description |
|---|---|---|---|
| biography | – | yes | – |
| caveat | string | yes | – |
| judge | object | yes | – |
| research | – | yes | – |
No examples provided.
get_judge_profile ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| judge_url | string | yes | Canonical profile_url returned by find_judges |
| Name | Type | Req | Description |
|---|---|---|---|
| before_you_appear | array | yes | – |
| biography | – | yes | – |
| biography_research | – | yes | – |
| findings | array | yes | – |
| judge | object | yes | – |
| scope_note | – | – | – |
| sources | array | yes | – |
| specialty_programs | array | – | – |
| summary | – | – | – |
No examples provided.
get_recent_rule_changes ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| court_url | string | – | Optional canonical court_url returned by find_court |
| judge_url | string | – | Optional canonical profile_url returned by find_judges |
| limit | integer | – | – |
| since | string | yes | Inclusive date in YYYY-MM-DD format |
| Name | Type | Req | Description |
|---|---|---|---|
| change_tracking_started_at | string | yes | – |
| results | array | yes | – |
| since | string | yes | – |
No examples provided.
How do I install the KnowJudges MCP server?
KnowJudges is a hosted endpoint at https://mcp.knowjudges.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.knowjudges.com
claude mcp add --transport http com-knowjudges-knowjudges 'https://mcp.knowjudges.com/mcp'
What is the KnowJudges MCP server?
KnowJudges is an MCP server listed in the public MCP registry as com.knowjudges/knowjudges. Source-linked research on U.S. judges, courts, cases, and judicial analytics. This page covers its hosted endpoint (https://mcp.knowjudges.com/mcp).
Is the KnowJudges MCP server safe to use?
KnowJudges scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the KnowJudges MCP server expose?
KnowJudges exposes 11 tools: find_judges, find_ai_abuse_cases, get_judge_profile, get_judge_biography, get_courtroom_presentation_rules, and 6 more. Their descriptions and schemas cost roughly 1,595 tokens of context every time the server is loaded.
Does the KnowJudges MCP server require authentication?
No. We connected to KnowJudges without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the KnowJudges MCP server still maintained?
KnowJudges is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.