GLO Law

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 法律与政府数据

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://mcp.glolaw.org/mcp

claude mcp add --transport http glo-law https://mcp.glolaw.org/mcp

{
  "mcpServers": {
    "glo-law": {
      "url": "https://mcp.glolaw.org/mcp"
    }
  }
}

{
  "servers": {
    "glo-law": {
      "type": "http",
      "url": "https://mcp.glolaw.org/mcp"
    }
  }
}

https://mcp.glolaw.org/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• search

  Case-name metadata search over the local CourtListener mirror. Punctuation-insensitive trigram match on the case name ("Brown v board of education" matches "Brown v. Board of Education"). Returns cluster rows: id, case_name, case_name_short, date_filed, precedential_status, citat

• fts

  Keyword full-text search (BM25) over opinion body text in the local mirror. Keyword, not concept: matches the exact words given (case-insensitive) with no stemming ("petition" does not match "petitions"); all words must appear; "double quotes" mark an exact phrase. A case that st

• semantic_search

  Semantic (vector) search over embedded opinion chunks: finds cases by concept or plain-language description when there is no fixed term of art. Returns one row per case: opinion_id, cluster_id, metadata, matched_chunk, distance, similarity, matched_text (the passage the case matc

• similar

  Given one opinion id, returns other opinions whose wording overlaps it, ranked by keyword match (BM25 more-like-this). Keyword overlap only: not a finding that the neighbors address the same issue, reach the same result or remain good law, and not complete. The seed opinion and i

• citation

  Resolves a reporter citation " " (e.g. 347 U.S. 483) to the matching case cluster(s) in the local mirror, optionally with member opinions and parallel citations. A 404 means the citation is not in this mirror, not that the case does not exist. A resolved citation shows the case i

• cluster

  Full case (cluster) detail by cluster id: cluster metadata, member opinions and parallel citations. Metadata only; the opinion tool returns full text. Every response carries a "note" stating that response’s source and coverage limits.

• opinion

  Full text of one opinion by opinion id, plus metadata. The text is the best stored text extracted from the mirror (HTML stripped; body_source names the extraction source and fallback_used flags a lower-precedence one), bounded to 200k characters with truncated and text_available

• citations

  Given one opinion id, lists the cases it cites (direction=authorities) or the cases that cite it (direction=cited_by). Textual reference only: an edge means one opinion’s text names the other; it is not treatment, agreement, validity or "good law", and not a Shepard’s or KeyCite

• parentheticals

  Given one opinion id, returns the one-line parentheticals later courts wrote about that case, verbatim. A parenthetical is the later court’s own characterisation: not a holding of the described case, not a summary written by this service, and not treatment, validity or "good law"

• treatment

  Later courts, in their own words, reporting that one case was overruled, abrogated, superseded, reversed or vacated. Takes a cluster id (the case-record id), not an opinion id. Every row carries the citing court’s own sentence, cut from its stored text; the label is a filter over

• brief_check

  Checks the case citations in a document the user supplies (a draft filing, brief or motion) against this collection and court-reported negative history, showing which cited cases to read before filing. Nothing is ever cleared: there is no pass mark or "verified" state. Per citati

• statute

  Exact lookup of one statute section or one regulation section by citation, in a point-in-time snapshot of published law. Returns the text verbatim with jurisdiction, corpus, citation, heading, path, source_url, as_of, act_status, last_amended_year and repaired. Enacted text only:

• statute_search

  Keyword (BM25) search over the body text of statute sections and, in the default source, Kansas administrative regulations, in the same snapshot as the statute tool; source= searches one regulation source alone. Without jurisdiction=, results mix states: on 6,852 benchmark housin

• statute_citing

  Lists the opinions whose text cites one U.S. Code section. Federal only: no state statute-citation links exist, and a state citation returns a visible error. An entry means the opinion’s text names the section; it does not say how the court treated it and carries no treatment, va

• corrections_policy

  Internal policies of a state department of corrections, or of the Federal Bureau of Prisons (state="bop", federal), as the department posts them, by number or by keyword search (query; no stemming). Not law: not statutes, regulations or court rules (a Maine policy the department

• deadline

  Counts a deadline from a date the user gives, under a rule whose text is in GLO’s mirror, and returns every counting step beside that text. Counted: K.S.A. 60-206 (Kansas civil procedure; a period in days the user supplies from the rule or order that sets it, forward or backward,

• sources

  Returns GLO’s coverage statements as text, so each tool’s and each source’s limits can be read on request. With a tool name alone: that tool’s full statement of coverage, measured limits and field meanings ("server" gives the full server overview). With a source or state code: fo

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（glolaw.org）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 153 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 17 个工具描述，未发现针对 AI 的隐藏指令

与“法律与政府数据”中的其他服务器比较i

• 星标数多于此分类中其他 1762 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1762 个服务器的 87% 更新
• 基础检查结果等于或优于此分类中其他 1762 个服务器的 40%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README