Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Pakistan Case Law is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search 230,000+ Pakistani court judgments by keyword, citation, or the legal question they settle.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pakistan-case-law-mcp https://pakistancaselaw.com/mcp
# 2 — ask your agent for something these tools do
# caselaw_search, caselaw_search_questions, caselaw_lookup_citation and 4 more
Pakistan Case Law costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PAAll 1 server
pakistancaselaw1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http pakistan-case-law-mcp https://pakistancaselaw.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Full-text search of Pakistani judgments (Supreme Court, High Courts, Federal Shariat Court and tribunals, 1970 onward), with optional filters by court, judge, 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 curre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | Keywords, e.g. 'bail murder 302' or 'khula dower'. May be left out when a filter is given. | |
| court | no | Only this court: 'Supreme Court', 'Lahore High Court' (or 'LHC'), 'Sindh High Court', 'Peshawar High Court', 'Islamabad High Court', 'Balochistan High Court', 'Federal Shariat Court', or a tribunal's | |
| judge | no | Only judgments where this judge sat on the bench. Spelling-tolerant: 'Asif Khosa', 'Qazi Faez Isa'. The reply names the judge it matched. | |
| journal | no | Only judgments reported in this law report: 'PLD', 'SCMR', 'CLC', 'YLR', 'PLC(CS)', 'PTD' ... With year_from/year_to it selects that volume, e.g. SCMR 2025. | |
| year_from | no | Earliest year (inclusive) | |
| year_to | no | Latest year (inclusive) | |
| limit | integer | no | — |
| offset | integer | no | — |
| sort | string | no | relevance (default: nearest on the point, then court/bench/recency/citations) | newest (the ~200 closest matches in strict date order) | court (most senior court first) | recently_added (newest additi |
| response_format | string | no | — |
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 u
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The legal question or its subject, in the words a judgment would use — 'delay in lodging FIR', 'concurrent findings of fact', 'pre-arrest bail murder' |
| court | no | Only this court, e.g. 'Supreme Court' or 'Lahore High Court' | |
| judge | no | Only judgments where this judge sat on the bench (spelling-tolerant, e.g. 'Mansoor Ali Shah') | |
| year_from | no | Earliest year (inclusive) | |
| year_to | no | Latest year (inclusive) | |
| limit | integer | no | — |
| offset | integer | no | — |
| response_format | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| journal | string | yes | Law-report code, e.g. 'PLD', 'SCMR', 'CLC' |
| year | integer | yes | — |
| page | no | Page/serial number in the report (optional) | |
| limit | integer | no | — |
| offset | integer | no | — |
| response_format | string | no | — |
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 body text (capped at ~40,000 chars; the response flags body_truncated/body_chars_total when longer).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | Numeric judgment id (from a search/lookup/graph result) |
| section | string | no | 'summary' = metadata + headnote (cheap); 'full' = + judgment text |
| response_format | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | Numeric judgment id |
| limit | integer | no | — |
| offset | integer | no | — |
| response_format | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | integer | yes | Numeric judgment id |
| limit | integer | no | — |
| offset | integer | no | — |
| response_format | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| offset | integer | no | — |
| response_format | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Pakistan Case Law or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.5.0.
1.5.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Pakistan Case Law can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.