Skip to content

MCP servers › org.glolaw › glo-law

MCP server · registry snapshot 2026-11-04 · last tested 2026-11-04

glo-law MCP server

Registry name org.glolaw/glo-law

by glolaw.org · domain (the registry's namespace rule)Website ↗

Free U.S. legal research: court opinions, statutes, state regulations and corrections policies. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-04version 1.0.1streamable HTTP17 tools

Summary

org.glolaw/glo-law is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain glolaw.org. On 2026-11-04 ProtocolProbe connected to it in read-only mode and read its inventory: 17 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
17
Last tested
2026-11-04

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-04 (mcp.glolaw.org), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.1).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-04
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-11-03 (registry, as of the 2026-11-04 snapshot)
First listed version
2026-11-03 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-11-03; 2 in the 90 days before the 2026-11-04 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-11-03
  • 1.0.0 · 2026-11-03
(versions still listed in the registry only)
Registry data
snapshot 2026-11-04
Package and repository
checked 2026-11-04
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-03, listed on 2026-11-04 with version 1.0.1 (published 2026-11-03).

Source: the official MCP Registry list on 2026-11-03 and on 2026-11-04.

What it is

What does this server offer?

Observed inventory
17tools
0resources
0prompts

None of its 17 tools are described as changing anything. For 17 the reading was uncertain, so no mark is shown.

  • “Case-name metadata search over the local CourtListener mirror.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs, 1 required
    • qstringrequired“case name or fragment (>=3 chars)”
    • courtarray“filter to CourtListener court ids (e.g.”
    • date_filed_afterstring“only cases filed on/after this date (YYYY-MM-DD)”
    • date_filed_beforestring“only cases filed on/before this date (YYYY-MM-DD)”
    • precedential_statusarray“filter by precedential status; OR within the list”
    • min_citation_countinteger“minimum citation_count”
    • sortstring“order: citation (default), date, date_asc”
    • limitinteger“max results, 1-20 (default 20)”
  • fts

    “Keyword full-text search (BM25) over opinion body text in the local mirror.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs, 1 required
    • qstringrequired“keywords; all must appear, no stemming; "quotes" = exact phrase”
    • courtarray“filter to CourtListener court ids (e.g.”
    • date_filed_afterstring“only cases filed on/after this date (YYYY-MM-DD)”
    • date_filed_beforestring“only cases filed on/before this date (YYYY-MM-DD)”
    • precedential_statusarray“filter by precedential status; OR within the list”
    • min_citation_countinteger“minimum citation_count”
    • limitinteger“max results, 1-20 (default 20)”
  • semantic_searchon 31 other servers

    “Semantic (vector) search over embedded opinion chunks: finds cases by concept or plain-language description when there is no fixed term of art.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • qstringrequired“a concept or plain-language description of the legal issue”
    • limitinteger“max results, 1-20 (default 20)”
  • “Given one opinion id, returns other opinions whose wording overlaps it, ranked by keyword match (BM25 more-like-this).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • idintegerrequired“seed OPINION id (from a search/fts/semantic result opinion_id)”
    • limitinteger“max results, 1-20 (default 20)”
  • “Resolves a reporter citation "<volume> <reporter> <page>" (e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • citestringrequired“"<volume> <reporter> <page>", e.g.”
    • includearray“extra data to attach: "opinions" (member opinions), "citations" (parallel cites)”
  • “Full case (cluster) detail by cluster id: cluster metadata, member opinions and parallel citations.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idintegerrequired“cluster id (from a search/fts/citation result: id or cluster_id)”
  • opinion

    “Full text of one opinion by opinion id, plus metadata.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idintegerrequired“opinion id (from a search/fts/semantic/similar result opinion_id)”
  • “Given one opinion id, lists the cases it cites (direction=authorities) or the cases that cite it (direction=cited_by).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • idintegerrequired“seed OPINION id (from a search/fts/semantic/similar result opinion_id)”
    • directionstring“authorities = cases THIS opinion cites; cited_by = cases that cite THIS one (default cited_by)”
    • limitinteger“max in-corpus results, 1-50 (default 25)”
    • with_passagesboolean“cited_by only: also return each citing court's verbatim sentence around the citation (citing_passage).”
  • parentheticals

    “Given one opinion id, returns the one-line parentheticals later courts wrote about that case, verbatim.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • idintegerrequired“the DESCRIBED opinion id — the case you want later courts' descriptions of (from a search/fts/semantic/similar result opinion_id)”
    • limitinteger“max groups returned, 1-25 (default 10); one representative parenthetical per group”
  • treatment

    “Later courts, in their own words, reporting that one case was overruled, abrogated, superseded, reversed or vacated.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • cluster_idintegerrequired“the CASE RECORD (cluster) id of the case you are checking — from a search/citation/fts result (id or cluster_id), not an opinion id”
    • labelstring“filter rows to one label.”
    • limitinteger“max rows returned, 1-25 (default 10)”
    • offsetinteger“skip this many, for paging further down the date order; capped at 5000”
  • 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 filin…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • textstringrequired“the document text to check, as plain text.”
  • statute

    “Exact lookup of one statute section or one regulation section by citation, in a point-in-time snapshot of published law.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • citestring“full citation as published, e.g.”
    • jurisdictionstring“jurisdiction code, e.g.”
    • sectionstring“section number as the publisher prints it, e.g.”
    • titlestring“optional title or chapter number narrowing a jurisdiction+section lookup; with source="cfr" the CFR title, required with section; for other sources the forms a…”
    • rawboolean“statutes only: true returns the stored text unchanged, without the page-overlap repeat removal”
    • sourcestring“omit for statutes and Kansas regulations; a regulation source code ("cfr" for federal, or a state code) reaches that source alone; each code’s coverage and cit…”
Show 5 more tools
  • 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=<code> searches one regula…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 1 required
    • qstringrequired“words to match in the statute section text.”
    • jurisdictionstring“restrict to one jurisdiction, e.g.”
    • limitinteger“max results, default 20, capped at 50”
    • sourcestring“omit for statutes and Kansas regulations; a regulation source code ("cfr" for federal, or a state code) searches that source alone; each code’s coverage is giv…”
    • titlestring“only with source=: narrows the search to one title, part or chapter of that source; the forms per source are given by sources(tool="statute_search", source=<co…”
  • statute_citing

    “Lists the opinions whose text cites one U.S.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs
    • citestring“federal citation as published, e.g.”
    • titlestring“U.S.”
    • sectionstring“U.S.”
    • limitinteger“max citing opinions returned, default 25, capped at 50”
    • offsetinteger“skip this many, for paging further down the date order; capped at 5000”
  • 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).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • statestringrequired“the department: a state code (e.g.”
    • numberstring“a procedure, section, directive or policy number as the department prints it, e.g.”
    • querystring“words to match in the policies’ text (keyword, no stemming).”
    • limitinteger“max search results, default 20, capped at 50 (search only)”
  • “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 2 required
    • rulestringrequired“the rule: "ks-60-206" (K.S.A.”
    • start_datestringrequired“YYYY-MM-DD: for ks-60-206, frcp-6 and frap-26 the day the period runs from (or the event it counts back from); for kar-44-15-101b the day the event was discove…”
    • daysinteger“ks-60-206, frcp-6 and frap-26: the period in days, 1 to 3650, from the rule or order that sets it (usc-28-2107-a: omit, or 30)”
    • directionstring“ks-60-206, frcp-6 and frap-26: "after" (default) or "before" the start date”
    • servicestring“ks-60-206, frcp-6 and frap-26: how the paper was served.”
    • event_datestring“kar-44-15-101b only, required: YYYY-MM-DD, the day of the event itself (the one-year limit)”
  • “Returns GLO’s coverage statements as text, so each tool’s and each source’s limits can be read on request.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • toolstringrequired“a tool name, or "server" for the full server overview”
    • sourcestring“optional: a regulation source code for statute or statute_search (e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-04.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 62
Tools with a description
100% of 17
Typical description length
1,241 characters

The tool set

Counted from the listing

Tools
17
Size of the list
about 10,113 tokens for an agent to load (characters ÷ 4)
Naming
12 of 17 names use single lower-case words

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 17 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-04 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.glolaw.org/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "glo-law": {
      "url": "https://mcp.glolaw.org/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "glo-law": {
      "type": "http",
      "url": "https://mcp.glolaw.org/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"glo-law","type":"http","url":"https://mcp.glolaw.org/mcp"}'
Claude Code
claude mcp add --transport http glo-law https://mcp.glolaw.org/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "glo-law": {
      "type": "streamableHttp",
      "url": "https://mcp.glolaw.org/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "glo-law": {
      "httpUrl": "https://mcp.glolaw.org/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.glo-law]
url = "https://mcp.glolaw.org/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "glo-law": {
      "url": "https://mcp.glolaw.org/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.glolaw.org/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.glolaw.org/mcpSession openedmatchesour test · 2026-11-04
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-04

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-04. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about org.glolaw/glo-law

Answered from the data above

Who publishes org.glolaw/glo-law?

The registry ties the namespace org.glolaw to the domain glolaw.org; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does org.glolaw/glo-law need an API key or sign-in?

It opened a session without any credential on 2026-11-04. The registry entry declares no required credential; no declaration is not a guarantee.

Has org.glolaw/glo-law been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-04
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-04, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,945 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 17 tools, 0 resources, 0 prompts.
  4. 8,218 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-11-04; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-04
MCP capability
tools
our test · 2026-11-04
Transport
streamable HTTP
registry · 2026-11-04
Required credentials
none declared
registry · 2026-11-04 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-04
Lifecycle status
registry · 2026-11-04
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-04

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “org.glolaw/glo-law: MCP server record.” Data checked 2026-11-04. https://protocolprobe.com/mcp/servers/org.glolaw/glo-law

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/org.glolaw/glo-law)](https://protocolprobe.com/mcp/servers/org.glolaw/glo-law)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology