KnowJudges

com.knowjudges由 knowjudges.com 发布官方发布者v0.10.15更新于 Oct 25, 2026

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

已验证Streamable HTTP可网页运行知识与记忆数据与分析

概览

AI 生成的概览

一个只读的远程 MCP 服务器,用于检索美国法官、法院、法律 AI 错误案例及移民裁决统计的来源可追溯研究资料。

可以做什么
按姓名、州、县或辖区查找法官和法院,并获取后续查询所需的标准资料链接。读取法官公开资料、有来源的传记以及法庭陈述或出庭规则。获取法院身份、元数据以及有数量上限的在册法官名单。检索已报道的法律 AI 错误案例(如伪造引证),含制裁结果和日期筛选。查看指定日期以来记录的法官资料或规则变更。按国籍、州和年份查询并比较移民法官或法院的裁决比率,并标注样本量。
适用场景
适合需要回答某位美国法官的背景或出庭要求、查询法院信息或法官名单、核查法律文书中已报道的 AI 伪造案例,或比较移民裁决统计数据的情形。它是研究辅助工具,不能用于提交文件或案件管理。
运行要求
在客户端的 MCP 设置中添加远程 Streamable HTTP 端点,仅需 URL 即可配置。有限度的公开访问无需令牌。需要能访问该端点的网络。请求按 IP 或服务商会话限流,并对每日新访问的法官和法院身份设有上限。
安装前请注意
所有工具均为只读,不能提交文件、联系法官或修改记录。结果有数量上限(每次搜索最多 10 条,变更记录最多 25 条),不提供分页或批量导出;批量或长期使用需另行申请数据授权。移民比率是历史汇总数据,不是预测,小样本会被标注。缺失数据表示不可用,而非零或允许。请保留来源链接、日期和已说明的不确定性,并在依赖前核实所链接的来源。

安装

在 SourceWeft 中

  1. 打开 控制台中的 KnowJudges,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.knowjudges%2Fknowjudges/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "knowjudges": {
      "type": "http",
      "url": "https://mcp.knowjudges.com/mcp"
    }
  }
}

README

KnowJudges MCP

Source-linked U.S. judge, court, legal-AI case, and immigration-outcome research through a read-only remote MCP server.

Current contract

The deployed server advertises 10 tools. This reference was checked against live tools/list on October 12, 2026. Discover the deployed inputSchema and outputSchema rather than assuming a client’s cached catalog is current. All tools return structured, source-linked public results and advertise readOnlyHint: true, destructiveHint: false, and openWorldHint: false. They cannot file documents, email judges, or change records.

Connect

Add the endpoint in your client's remote MCP settings. Configuration names vary; a URL-only setup is sufficient where supported.

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

Tools and inputs

Optional inputs are omitted when not needed. Dates use YYYY-MM-DD. State/jurisdiction codes in schemas that require two letters are case-insensitive.

ToolPurpose and selection guidanceRequired inputsOptional inputs and limits
find_judgesResolve a named or otherwise identifiable judge. Results include profile_url and reported service status; named matches may be historical or uncertain.query (at least 2 characters)state (name or postal code), court, county, limit (default 5, 1–10).
get_judge_profileRetrieve identity, assignments, public profile information, sources, and scoped findings. Use the biography/practice tools for those focused questions.judge_urlNone. Missing fields mean information is unavailable. An assignment end date alone does not establish retirement or a senior-status transition.
get_judge_biographyRetrieve sourced birth details, education, professional career, and judicial service.judge_urlNone. Preserve date precision. Age is null unless a valid full birth date is available; year-only dates must not become precise ages.
get_courtroom_presentation_rulesAnswer a named judge’s courtroom-practice question using relevant findings and underlying sources. Do not detour into court metadata or rosters unless asked.judge_urltopics (up to 10 strings), such as exhibits, remote testimony, or a named part. Conditional program/division guidance remains conditional.
find_ai_abuse_casesSearch reported legal-AI error cases by case name, error type, or recorded outcome. response distinguishes sanctions from no sanctions.No single field is required by the schema; provide meaningful identifying search text or narrowing filters. Empty/bulk searches are unavailable.query (at least 2 characters), state, court, judge, response, inclusive from_date/to_date, limit (default 5, 1–10). Returned total_matches is not the number of supplied records.
get_recent_rule_changesRetrieve recorded profile/rule updates since a date. Court filtering also includes associated indexed judge profiles; ambiguous court-only records are omitted.since (inclusive date)judge_url, court_url, limit (default 10, 1–25). Tracking starts at returned change_tracking_started_at; empty results do not prove no earlier real-world changes.
find_courtResolve court identity for court metadata or roster questions.query (at least 2 characters)jurisdiction (2-letter code, e.g. GA, DC, US), state (name or postal code), limit (default 5, 1–10). Returns canonical court_url values.
get_courtRetrieve one court’s identity, available metadata, and bounded indexed current-status roster.court_urllimit (default 10, 1–10). Preserve roster_coverage and roster_truncated. Counts include indexed active, senior, recalled, or visiting profiles, not an independently verified complete bench.
get_immigration_analyticsRetrieve recorded outcomes for one immigration judge or court.entity (judge or court), profile_url (canonical public judge or court URL)metric (default asylum_denial_rate; alternative proceeding_removal_rate only when explicitly requested), year (1950–2100), year_basis (calendar, default, or fiscal), nationality (2–100 characters), state (2-letter code).
compare_immigration_analyticsCompare highest/lowest recorded judge or court rates with joint geography, nationality, and period filters.entity (judge or court)metric, year, year_basis, nationality, state as above; order (ascending, default, or descending), minimum_decisions (default 1, 1–100000), limit (default 3, 1–10).

For asylum analytics, percentages use grants plus denials; procedural outcomes are reported separately. Samples below 35 decisions are labeled rather than hidden. Zero decisions mean no rate, not 0%. Keep availability, message, denominator/geography definitions, source, period coverage, and limitations. Historical rates neither predict an individual outcome nor imply that a person can choose a judge.

Canonical public URL chaining

Use URLs returned by discovery, preserving their exact jurisdiction-qualified form. Do not construct URLs from names or use bare slugs, internal keys, or IDs.

Judge profile, biography, or practice

text
find_judges({"query":"Amy Totenberg","state":"GA","limit":3})→ select the matching results[i].profile_url→ get_judge_profile({"judge_url": selectedProfileUrl})        // identity/assignments→ get_judge_biography({"judge_url": selectedProfileUrl})      // biography question→ get_courtroom_presentation_rules({"judge_url": selectedProfileUrl}) // practice question

The follow-ups are alternatives selected by the question, not a requirement to call all three. profile_url in a discovery result becomes judge_url in these tool inputs.

Court information and recorded changes

text
find_court({"query":"U.S. District Court for the Northern District of Georgia","state":"GA"})→ select the matching results[i].court_url→ get_court({"court_url": selectedCourtUrl,"limit":5})→ get_recent_rule_changes({"since":"2026-10-01","court_url": selectedCourtUrl})

A judge-specific change lookup instead uses judge_url from judge discovery. An empty court roster means no indexed current matches; a null count means roster data is unavailable. Neither establishes the actual court has no judges. Retain location-specific contact notes rather than treating one courthouse's address or phone as courtwide.

Legal-AI cases

json
{  "name": "find_ai_abuse_cases",  "arguments": {    "query": "AI hallucinations fabricated legal citations",    "response": "Monetary Sanctions",    "limit": 5  }}

Report the recorded outcome and preserve the returned decision-link status; inclusion in the dataset alone does not establish a judicial finding that AI was used.

Immigration comparisons

text
compare_immigration_analytics({"entity":"judge","nationality":"Brazil","state":"CA","year":2025,"order":"ascending","limit":3})→ lowest recorded asylum denial rates for the available filtered periodcompare_immigration_analytics({"entity":"judge","nationality":"Brazil","state":"CA","year":2025,"order":"descending","limit":3})→ highest recorded rates; retain counts, small-sample notes, and coverage→ get_immigration_analytics({"entity":"judge","profile_url": returnedProfileUrl,"nationality":"Brazil","state":"CA","year":2025})

Use an available, non-null returned public URL for the follow-up. These examples illustrate inputs; they do not guarantee data for a particular nationality/year.

Bounds, quotas, and anti-enumeration

  • Searches, court rosters, and immigration comparisons return at most 10 records. Recent changes return at most 25. Practice-topic filters accept at most 10 topics.
  • No pagination, cursor, offset, batch enumeration, or bulk export is provided. Empty, wildcard, one-character, jurisdiction-only judge/court searches, and requests for all judges/courts are rejected. Use identifying name/location text plus narrowing filters.
  • Sequential prefix/identifier harvesting is throttled. Daily unique judge/court budgets count a previously accessed identity only once; changing conversation sessions does not reset an OpenAI subject's quota.
  • Generic anonymous callers use the IP fallback: 20 tool requests/hour, 100/day, and 50 newly accessed judge/court identities/day.
  • OpenAI callers supplying _meta["openai/subject"] use an anonymous subject bucket: 60 tool requests/hour, 300/day, and 100 new identities/day. openai/session is not a durable quota key.
  • Recognized Claude requests use session context when available for short-term control; no durable per-user identifier is inferred. Without a session, aggregate network controls apply. Session allowances are 60/hour, 300/day, and 100 new identities/day.
  • A separate recognized-provider IP/network backstop allows 1000 requests/hour, 10000/day, and 1000 new identities/day. Ordinary networks have a 200/hour, 1000/day backstop and a 100-new-identity/day network budget. These are aggregate ceilings, not individual entitlements.
  • MCP initialization/discovery/control requests count toward the network backstop, not the normal caller tool quota. REST uses the shared enforcement implementation and anonymous fallback when no MCP caller context exists.
  • Rate/harvesting limits can return HTTP 429 or a bounded MCP tool failure. Respect retry information; do not rotate identities to bypass controls. Invalid inputs and missing data are different states.

For datasets or recurring/bulk use, see https://knowjudges.com/data-licensing.

Sources and verification

Keep returned KnowJudges URLs, source/official URLs, source titles, excerpts, scope/applicability, effective/revision dates, and last-checked dates where present. Judge-specific, courtwide, statewide, and nationally applicable federal/EOIR guidance are different authority scopes. Broader rules are not personal preferences. Missing documented practice findings establish neither permission nor prohibition.

last_updated describes publication, while last_verified or source_checked_at describes an evidence check. A recent publication does not mean every source was checked that day. Preserve supported year-only biography dates and factual uncertainty.

AI-case links may be verified decision destinations or explicitly labeled source fallbacks. Preserve decision_link_status, dataset_source, and summary_note; a fallback URL must not be described as a verified official court decision. Unknown ruling counts are unavailable, not zero. Check the linked source before relying on a requirement; case-specific orders may control.

Links

Third-party listings and client tool catalogs may lag a release; live tools/list is authoritative.

来源:README.md,提交 2382d17

工具

11

find_judges

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.

输入参数courtlimitquery必填statecounty

find_ai_abuse_cases

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.

输入参数courtjudgelimitquerystateto_dateresponsefrom_date

get_judge_profile

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.

输入参数judge_url必填

get_judge_biography

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.

输入参数judge_url必填

get_courtroom_presentation_rules

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.

输入参数topicsjudge_url必填

get_recent_rule_changes

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.

输入参数limitsince必填court_urljudge_url

find_court

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.

输入参数limitquery必填statejurisdiction

get_court

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.

输入参数limitcourt_url必填

get_immigration_analytics

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.

输入参数yearstateentity必填metricyear_basisnationalityprofile_url必填

compare_immigration_analytics

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.

输入参数yearlimitorderstateentity必填metricyear_basisnationalityminimum_decisions

get_directory_counts

Get Core counts for Judges, Courts and Courthouses nationally or by state. Judges include historical profiles; Courts are institutions; Courthouses are known physical addresses. Shared addresses count once.

输入参数state

版本历史

1
  1. v0.10.15最新Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。