Global law MCP server
com.lexifina/global-lawlexifina.comstreamable-httpv1.1.1Scanned
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
18 tools: 10 change things and 8 only read.
- Reads private data · 4
- Reads text others write · 3
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
10 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Global law MCP server can do
The Global law MCP server is published by lexifina.com, a domain the MCP Registry verified. It has 18 tools. It can create or change data (10 tools: world_on_date, who_wrote, provision_history, laws_between and 6 more), but cannot delete data. 8 tools only read.
4 tools read private data (find_provision, list_provisions, search_changes and 1 more); 3 tools bring in text other people can write (list_provisions, search_changes and resolve_citations).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
18 tools
Changes things 10Claude Code: ask
applies_to_caseFor a case commenced on one date, which later changes to a provision reach it (from any scope the record holds, such as "cases commenced on or after"), and the text that applies to…1 finding
Why it is in this group
- The name "applies_to_case" says "apply": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "applies_to_case" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "applies_to_case" says "apply": a word for a change.
Description, as the server wrote it For a case commenced on one date, which later changes to a provision reach it (from any scope the record holds, such as "cases commenced on or after"), and the text that applies to it.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
changes_betweenEvery provision whose text differs between two dates, in every jurisdiction or one, with the laws that changed them.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every provision whose text differs between two dates, in every jurisdiction or one, with the laws that changed them.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
check_precedentFor case law: a court applied a provision on the day it decided.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it For case law: a court applied a provision on the day it decided. Is that text still the text in force (today, or on a date), and if not, which laws changed it and how? Also lists judgments the record holds for the provision.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
law_detailsThe full record of a law's change: its commit message with every trailer (enacted, in force, published, sources, scope), the provisions it changed, and what it did to each one's wo…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The full record of a law's change: its commit message with every trailer (enacted, in force, published, sources, scope), the provisions it changed, and what it did to each one's words (a word diff, or "layout only", or "text moved between provisions"). One call answers "what did this law change"; no need to compare each provision.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
laws_betweenEvery law that took effect between two dates, across all jurisdictions or one, in the order they took effect.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every law that took effect between two dates, across all jurisdictions or one, in the order they took effect.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
phrase_historyWhen words came into the law and when they left it, at any date and in every jurisdiction: each change whose added or removed text contains them.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it When words came into the law and when they left it, at any date and in every jurisdiction: each change whose added or removed text contains them. Use it for things no longer in force (for example "COVID" in the Grundgesetz).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
provision_historyEvery law that changed a provision, oldest first, with its in-force, enacted or made, and published dates.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every law that changed a provision, oldest first, with its in-force, enacted or made, and published dates.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
what_else_changesWhich provisions rely on, cite or use the definitions of this one, on a date: those that cite it, and those that use a term it defines (for example the provisions that use "debtor …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Which provisions rely on, cite or use the definitions of this one, on a date: those that cite it, and those that use a term it defines (for example the provisions that use "debtor in possession"), with the definition's scope ("In this subchapter"). Use it before a text search when asked what depends on a provision or its definitions; a change to this provision can change what they mean.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
who_wroteWhich law wrote each word (or each line) of a provision as it stood on a date, with a count of words per law.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Which law wrote each word (or each line) of a provision as it stood on a date, with a count of words per law.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
world_on_dateWhat every jurisdiction in the tree looked like on one date: the last change in force in each, and the next.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it What every jurisdiction in the tree looked like on one date: the last change in force in each, and the next.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
Only reads 8Show 8 read-only tools
compare_datesHow a provision changed between two dates: a word-level diff and the laws that took effect in between.No findings
Why it is in this group
- The name "compare_dates" says "compare": a word for reading.
Description, as the server wrote it How a provision changed between two dates: a word-level diff and the laws that took effect in between.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
find_provisionFind the file path of a provision by its number ("1182", "Art.Reads private dataNo findings
Why it is in this group
- The name "find_provision" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "file": it reads files.
Description, as the server wrote it Find the file path of a provision by its number ("1182", "Art. 16a", "reg 13") or words from its heading ("debtor", "Asylrecht").
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_jurisdictionsList every jurisdiction and body of law in the tree, with how far each record reaches and an example path.No findings
Why it is in this group
- The name "list_jurisdictions" says "list": a word for reading.
Description, as the server wrote it List every jurisdiction and body of law in the tree, with how far each record reaches and an example path. Start here.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_provisionsBrowse a corpus: the provision files under a corpus or folder (for example united-states/federal/usc/title-11), with headings, as in force on a date.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_provisions" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "browse" and "file": it reads files.
- private-dataThe input names a folder (input.by_folder), and the tool reads: it reads files.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse a corpus: the provision files under a corpus or folder (for example united-states/federal/usc/title-11), with headings, as in force on a date. For a folder of acts or instruments, by_folder gives one row each with its title and last change; a partial name lists the folders that start with it (malta/national/acts/sl/586. for every instrument made under Cap. 586).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
read_lawThe text of a provision as it was in force on a date, with the law that last changed it, the next change, and any limit of the record that applies.No findings
Why it is in this group
- The name "read_law" says "read": a word for reading.
Description, as the server wrote it The text of a provision as it was in force on a date, with the law that last changed it, the next change, and any limit of the record that applies.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
resolve_citationsRead every citation in a piece of text (a brief, a judgment, an email) and resolve each to its provision, with its state on a date: in force or not, the law that last changed it, a…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "resolve_citations" says "resolve": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "read" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it Read every citation in a piece of text (a brief, a judgment, an email) and resolve each to its provision, with its state on a date: in force or not, the law that last changed it, and the next change.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
search_changesSearch the record of changes (each commit message: the law, its dates, what it did) rather than the text of the law.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_changes" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "commit": it reads repositories.
- untrusted-inputThe description's first sentence says "search" and "message": it reads messages, which other people can write.
Description, as the server wrote it Search the record of changes (each commit message: the law, its dates, what it did) rather than the text of the law. For example "temporary", "COVID", "Bundesrat".
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
search_lawSearch the text of all the law in force on a date, across every jurisdiction or one.No findings
Why it is in this group
- The name "search_law" says "search": a word for reading.
Description, as the server wrote it Search the text of all the law in force on a date, across every jurisdiction or one. Plain text by default.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:21 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 10
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 10 tools that change things (10 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://global-law.lexifina.com/mcp: tools/list returned 18 tools to an anonymous client, including world_on_date (write), who_wrote (write), provision_history (write), laws_between (write), changes_between (write) and 5 more
Findings
Matches of fixed checks, with the text they matched.
- Warnapplies_to_case
The server marks "applies_to_case" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "applies_to_case" says "apply": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http global-law https://global-law.lexifina.com/mcpclaude mcp add --transport http global-law https://global-law.lexifina.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__global-law__list_jurisdictions",
"mcp__global-law__find_provision",
"mcp__global-law__read_law",
"mcp__global-law__compare_dates",
"mcp__global-law__search_law",
"mcp__global-law__list_provisions",
"mcp__global-law__search_changes",
"mcp__global-law__resolve_citations"
],
"ask": [
"mcp__global-law__world_on_date",
"mcp__global-law__who_wrote",
"mcp__global-law__provision_history",
"mcp__global-law__laws_between",
"mcp__global-law__changes_between",
"mcp__global-law__check_precedent",
"mcp__global-law__what_else_changes",
"mcp__global-law__phrase_history",
"mcp__global-law__applies_to_case",
"mcp__global-law__law_details"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as global-law. Review it before you use it.
Capability tags behind 4 rules
- mcp__global-law__find_provision private-data
- mcp__global-law__list_provisions private-data, untrusted-input
- mcp__global-law__search_changes private-data, untrusted-input
- mcp__global-law__resolve_citations private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.lexifina/global-law/verify?hash=32308fc2186ad0171f935fb7d104f55315664e404837f2834027e258e24ae798" | jq -e '.changed == false'Pinned hash 32308fc2186a, from Nov 10, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.lexifina/global-law/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.lexifina/global-law)Source: MCP Registry · repository. Synced Nov 10, 2026, 11:17 UTC.
Global law MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Global law MCP server safe?
- No scan can promise that. What its definitions show: 18 tools, 10 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Global law MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Global law MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Global law MCP server have?
- 18 tools: 10 write, 8 read. world_on_date, who_wrote, provision_history, laws_between, changes_between, check_precedent, what_else_changes, phrase_history and 10 more.
Does the Global law MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Global law MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Global law MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.