Pakistan Case Law MCP server
com.pakistancaselaw/caselawpakistancaselaw.comstreamable-httpv1.6.1Scanned
Search 230,000+ Pakistani court judgments by keyword, citation, or the legal question they settle.
7 tools: 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- 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 Pakistan Case Law MCP server can do
The Pakistan Case Law MCP server is published by pakistancaselaw.com, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.6.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.
7 tools
Only reads 7Show 7 read-only tools
caselaw_get_caseFetch one judgment by id.No findings
Why it is in this group
- The name "caselaw_get_case" says "get": a word for reading.
Description, as the server wrote it Fetch one judgment by id. section='summary' (default) returns metadata + the headnote (plain-language summary, the laws/provisions referred, and keyword tags) — read this first to judge relevance cheaply. section='full' additionally returns the judgment text; a long judgment arrives in its first part and says so. Long judgment: section='outline' gives a map (the judge's paragraph numbers, each separate opinion, the order), then paras='41-55' reads exactly those paragraphs (paras='2:3-5' = opinion 2, paragraphs 3-5, where separate opinions each restart their numbers), find='words' returns the paragraphs of this judgment that match, and start=N continues from a character position. These return the court's own words, never a summary.
Annotations the server declares
- title: Get a judgment
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
caselaw_get_citationsWalk the citation graph FORWARD: list the in-corpus cases that THIS judgment cites (the precedents it relied on).No findings
Why it is in this group
- The name "caselaw_get_citations" says "get": a word for reading.
Description, as the server wrote it Walk the citation graph FORWARD: list the in-corpus cases that THIS judgment cites (the precedents it relied on). Combine with caselaw_get_cited_by to traverse precedent backward and forward until a research question is resolved. Most useful on RECENT judgments: a 2024-25 case usually has nobody citing it yet, but its own citation list is a curated map of the established authority on the point.
Annotations the server declares
- title: Cases this judgment cites (forward)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
caselaw_get_cited_byWalk the citation graph BACKWARD: list later cases that cite THIS judgment (how it was subsequently treated — followed, distinguished, relied upon).No findings
Why it is in this group
- The name "caselaw_get_cited_by" says "get": a word for reading.
Description, as the server wrote it Walk the citation graph BACKWARD: list later cases that cite THIS judgment (how it was subsequently treated — followed, distinguished, relied upon). Returns newest first. Most useful on OLDER or landmark judgments: it shows whether the case is still followed and where the principle has been applied since. A leading case can have hundreds of citing cases.
Annotations the server declares
- title: Later cases citing this (backward)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
caselaw_lookup_citationFind the judgment(s) at an exact law-report citation.No findings
Why it is in this group
- The name "caselaw_lookup_citation" says "lookup": a word for reading.
Description, as the server wrote it Find the judgment(s) at an exact law-report citation. Example: journal='PLD', year=1995, page=34 → PLD 1995 Supreme Court 34. Omit page to list everything reported in that journal+year. Returns the same case shape as caselaw_search.
Annotations the server declares
- title: Look up a citation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
caselaw_most_citedList the most-cited (landmark) judgments in the corpus, ranked by how many other cases cite them.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List the most-cited (landmark) judgments in the corpus, ranked by how many other cases cite them. A good entry point for the leading authorities on Pakistani law.
Annotations the server declares
- title: Most-cited landmark cases
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
caselaw_searchFull-text search of Pakistani judgments (Supreme Court, High Courts, Federal Shariat Court and tribunals, 1970 onward), with optional filters by court, judge, author, law report an…No findings
Why it is in this group
- The name "caselaw_search" says "search": a word for reading.
Description, as the server wrote it Full-text search of Pakistani judgments (Supreme Court, High Courts, Federal Shariat Court and tribunals, 1970 onward), with optional filters by court, judge, author, law report and year. Ranking follows how lawyers research: nearness to the legal point decides which cases are returned; among comparably-near cases, more senior court > larger bench > more recent > more cited. For the current state of the law, add year_from (e.g. 2025); use sort='court' for the most authoritative first. With no query, the filters list judgments newest first - e.g. court='Supreme Court' gives the latest Supreme Court judgments, journal='PLD' with year_from=year_to=2024 gives that volume, and sort='recently_added' alone shows what was added to the site most recently. Returns cases with id, title, citation, court, year, outcome, author (the judge who wrote it, when known) and the public URL; a keyword search also gives the number of judges on the bench and the words of the judgment that matched. For an exact report citation use caselaw_lookup_citation. To read a case, pass its id to caselaw_get_case.
Annotations the server declares
- title: Search judgments
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
caselaw_search_questionsFind judgments by the QUESTION they settle, rather than by words they contain.No findings
Why it is in this group
- The name "caselaw_search_questions" says "search": a word for reading.
Description, as the server wrote it Find judgments by the QUESTION they settle, rather than by words they contain. Every judgment summary on this corpus records the questions that judgment actually decides — e.g. "Does delay in lodging the FIR by itself entitle the accused to bail?" This searches those questions, so it matches the shape a legal problem arrives in rather than the vocabulary a 1987 bench happened to use. COVERAGE IS PARTIAL: only some judgments have a summary with questions yet (the response's `coverage_note` gives the current live ratio, which keeps growing). An empty result means no *summarised* judgment matched — it does NOT mean no such judgment exists. Fall back to caselaw_search, which covers the whole corpus. The questions are prepared from the judgment text. They are a finding aid, not a holding: cite the judgment, never the question. Pass an id to caselaw_get_case to read it.
Annotations the server declares
- title: Search by the legal question a judgment settles
- readOnlyHint: true
- destructiveHint: false
- 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 private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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 20, 2026, 18:44 UTC, unchanged since Oct 22, 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
- 0
- 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
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 changed.~7 changedView diff
- Changed:caselaw_get_caseOnly readstitle
- Changed:caselaw_get_citationsOnly readstitle
- Changed:caselaw_get_cited_byOnly readstitle
- Changed:caselaw_lookup_citationOnly readstitle
- Changed:caselaw_most_citedOnly readstitle
- Changed:caselaw_searchOnly readstitleinputSchema
- Changed:caselaw_search_questionsOnly readstitle
Tools1 changed.~1 changedView diff
- Changed:caselaw_searchOnly readsdescription
Tools1 changed.~1 changedView diff
- Changed:caselaw_get_caseOnly readsdescriptioninputSchema
Install
Pinned to version 1.6.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http caselaw https://pakistancaselaw.com/mcpclaude mcp add --transport http caselaw https://pakistancaselaw.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__caselaw__caselaw_search",
"mcp__caselaw__caselaw_search_questions",
"mcp__caselaw__caselaw_lookup_citation",
"mcp__caselaw__caselaw_get_case",
"mcp__caselaw__caselaw_get_citations",
"mcp__caselaw__caselaw_get_cited_by",
"mcp__caselaw__caselaw_most_cited"
],
"ask": [],
"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 caselaw. Review it before you use it.
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.pakistancaselaw/caselaw/verify?hash=64add63c872dbbaeac776584e5785ab7a2e366a5103212f03dd927002bf95d70" | jq -e '.changed == false'Pinned hash 64add63c872d, from Nov 8, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.pakistancaselaw/caselaw/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.pakistancaselaw/caselaw)Source: MCP Registry. Synced Oct 23, 2026, 16:24 UTC.
Pakistan Case Law MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Pakistan Case Law MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Pakistan Case 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 Pakistan Case 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 Pakistan Case Law MCP server have?
- 7 tools: 7 read. caselaw_search, caselaw_search_questions, caselaw_lookup_citation, caselaw_get_case, caselaw_get_citations, caselaw_get_cited_by and caselaw_most_cited.
Does the Pakistan Case Law MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Pakistan Case 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 Pakistan Case Law MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.