Pakistan Case Law

com.pakistancaselawPublished by pakistancaselaw.comOfficial publisherv1.6.1Updated Oct 24, 2026

Search 230,000+ Pakistani court judgments by keyword, citation, or the legal question they settle.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Remote MCP server for searching 230,000+ Pakistani court judgments by keyword, citation, or the legal question they settle.

What you can do
  • Search judgments full-text with filters by court, judge, author, law report and year
  • Find cases by the legal question they decide, or look up an exact law-report citation
  • Fetch a judgment's headnote summary or its full text
  • Trace precedent forward to the cases a judgment cites and backward to later cases citing it
  • List the most-cited landmark judgments in the corpus
When to use it
Useful for legal research on Pakistani case law: finding authorities on a point of law, checking how a precedent has been treated, or locating a judgment from a citation. Suited to lawyers, researchers and anyone needing Pakistani judgments rather than general web search.
Requirements
A remote streamable HTTP endpoint at pakistancaselaw.com; no packages, environment variables or headers are declared, and no authentication is declared.
Before you install
The server is read-only in the tools listed, but results are a third-party corpus and should be verified against official law reports before being relied on. Queries and citations you submit go to the provider's service.

Installation

In SourceWeft

  1. Open Pakistan Case Law in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.pakistancaselaw%2Fcaselaw/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "pakistan-case-law": {
      "type": "http",
      "url": "https://pakistancaselaw.com/mcp"
    }
  }
}

Tools

7

caselaw_search_questions

Search by the legal question a judgment settles

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.

Parameterscourtjudgelimitqueryrequiredoffsetyear_toyear_fromresponse_format

caselaw_lookup_citation

Look up a citation

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.

Parameterspageyearlimitoffsetjournalrequiredresponse_format

caselaw_get_case

Get a judgment

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.

Parametersfindparasstartcase_idrequiredsectionresponse_format

caselaw_get_citations

Cases this judgment cites (forward)

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.

Parameterslimitoffsetcase_idrequiredresponse_format

caselaw_get_cited_by

Later cases citing this (backward)

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.

Parameterslimitoffsetcase_idrequiredresponse_format

caselaw_most_cited

Most-cited landmark cases

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.

Parameterslimitoffsetresponse_format

Version history

9
  1. v1.6.1LatestOct 23, 2026
  2. v1.6.0Oct 22, 2026
  3. v1.5.0Oct 17, 2026
  4. v1.4.7Oct 14, 2026
  5. v1.4.6Oct 3, 2026
  6. v1.4.5Oct 2, 2026
  7. v1.4.4Oct 1, 2026
  8. v1.4.0Oct 1, 2026
  9. v1.3.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.