# com.pakistancaselaw/caselaw (remote · pakistancaselaw.com)

Search 197,000+ Pakistani court judgments (1970-2025) and walk their citation graph.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- remote · `pakistancaselaw.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-pakistancaselaw-caselaw/pakistancaselaw.md), [page](https://verifymcp.io/servers/com-pakistancaselaw-caselaw/pakistancaselaw)

## Channel facts

- Endpoint: `https://pakistancaselaw.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-17.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1371 tokens (~228/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-pakistancaselaw-caselaw https://pakistancaselaw.com/mcp
```

### Codex

```toml
[mcp_servers.com-pakistancaselaw-caselaw]
url = "https://pakistancaselaw.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-pakistancaselaw-caselaw": {
      "type": "remote",
      "url": "https://pakistancaselaw.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-pakistancaselaw-caselaw --url https://pakistancaselaw.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-pakistancaselaw-caselaw:
    url: "https://pakistancaselaw.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-pakistancaselaw-caselaw": {
      "type": "http",
      "url": "https://pakistancaselaw.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-17 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-16 (score 71)

First indexed and scored.

## MCP tools (6)

### `caselaw_search` (~176 tokens)

Full-text search of 197,000+ Pakistani judgments (Supreme Court & High Courts, 1970–2025).

    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. Use sort='newest' when you need the current state of the law (later judgments
    supersede as statutes are amended), or sort='court' for the most authoritative first.

    Returns ranked cases with id, title, citation, court, year, a snippet, and the public URL.
    For an exact report citation use caselaw_lookup_citation. To read a case, pass its id to
    caselaw_get_case.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `caselaw_lookup_citation` (~85 tokens)

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.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `caselaw_get_case` (~99 tokens)

Fetch one judgment by id.

    section='summary' (default) returns metadata + the AI 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).

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `caselaw_get_citations` (~110 tokens)

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.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `caselaw_get_cited_by` (~92 tokens)

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.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

### `caselaw_most_cited` (~56 tokens)

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.

Input parameters:

- `params` (required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-pakistancaselaw-caselaw/pakistancaselaw#diagnostics

## Score history

- 2026-08-17: 71
- 2026-08-16: 71

## Links

- Remote endpoint: https://pakistancaselaw.com/mcp
- Website: https://pakistancaselaw.com/for-ai
- Changelog RSS feed: https://verifymcp.io/servers/com-pakistancaselaw-caselaw/pakistancaselaw.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-pakistancaselaw-caselaw/pakistancaselaw.json
- HTML version of this page: https://verifymcp.io/servers/com-pakistancaselaw-caselaw/pakistancaselaw