Skip to main content
Glama

pk-eli-mcp

MCP server for Pakistani law: 967 federal statutes and 1,414 Supreme Court of Pakistan judgments, full text, with a strict citation contract on every response.

Pakistan publishes no machine-readable legal API, so this connector is corpus-based: it serves two public HuggingFace mirrors of official sources instead of querying a government endpoint live.

Collection

Source

Snapshot

License

Federal statutes (967)

Pakistan_Laws_Dataset, collected from pakistancode.gov.pk PDFs (Ministry of Law and Justice)

2025-01-30

ODC-BY 1.0

Supreme Court judgments (1,414)

supreme-court-of-pak-judgments

2024-07-26

MIT

Honest limits, stated up front: both collections are static snapshots. Amendments after 2025-01-30 and judgments after 2024-07-26 are absent, and the judgment corpus is a subset of the Court's output. Every response repeats this in dataset_note. Verify currency against pakistancode.gov.pk and scp.gov.pk before relying on a provision.

Tools

Tool

What it does

pk_search_laws

Keyword search over the 967 federal statutes (title-weighted). First call downloads the 47 MB corpus once, then serves from cache.

pk_get_law

Full statute text by law_id (truncated at ~300,000 characters).

pk_case_search

Server-side full-text search over the Supreme Court judgments.

pk_get_decision

One judgment's full text, by row_idx or registry case_id.

pk_verify_citations

Anti-hallucination check: extracts Pakistani legal citations from any text and verifies each against the corpus.

pk_coverage

Declare what this connector covers, when each family was captured, and - explicitly - what it does NOT cover. Every gap carries a fallback.

Related MCP server: turath

Citation verification (pk_verify_citations)

Run it on a drafted answer, memo or pleading before it reaches a reader. The tool extracts every checkable citation and verifies it against the corpus:

  • statute sections: section 302 of the Pakistan Penal Code, section 10A of the Pakistan Study Centres Act, 1976, sections 6 and 7 of ..., sub-section (1) of section 6 of ...;

  • act coordinates: Act No. XLV of 1860, Ordinance No. LII of 2000 (Roman or Arabic);

  • Constitution articles: Article 184(3) of the Constitution (the tail is required - a bare Article 5 could be any instrument and is deliberately ignored);

  • Supreme Court registry citations: Crl.A. 93/2013, Criminal Appeal No. 93 of 2013.

The semantics are deliberately hard:

  • A cited section that does not exist makes the whole result HALLUCINATION_DETECTED with isError=true, plus a range hint of what does exist (section 999 does not exist in this act; 59 sections are machine-detectable in its text, numbered section 1-66).

  • NO_CITATIONS_FOUND is not a success - it means there was nothing to check.

  • A parenthetical description right after a citation (section 302 of the Pakistan Penal Code (punishment of qatl-i-amd)) is content-checked against the real provision text with a character-trigram match. A mismatch is a review signal, never a hard block.

  • Everything the tool could NOT check is listed in a structured gaps field. The judgment corpus is a subset and roughly half the statute PDFs carry no machine-readable coordinate header, so an unresolvable citation is reported as out_of_corpus ("existence UNKNOWN, not disproven"), never as a hallucination.

The parse-verify-report pattern is adapted from korean-law-mcp (MIT) - see THIRD_PARTY.md. The same pattern shipped first in it-eli-mcp v0.6.0; the fleet rollout plan lives in docs/VERIFY-ROLLOUT.md.

Citation contract

Pakistan has not deployed ELI. Every response still carries the fleet contract:

  • eli_uri - a stable, resolvable URL: the canonical pakistancode.gov.pk PDF for statutes, the dataset row URI for judgments. Never invented; see eli_note.

  • human_readable_citation - e.g. THE PRIVATISATION COMMISSION ORDINANCE, 2000 or Supreme Court of Pakistan, Crl.A. 93/2013.

  • source_url - where a human can read the same document.

Install

As a Claude plugin (Claude Code or the desktop app, needs uv); see plugin/README.md for what it sends and stores:

/plugin marketplace add matematicsolutions/pk-eli-mcp
/plugin install pk-eli-mcp@pk-eli-mcp

As a standalone server:

uvx pk-eli-mcp          # or: pip install pk-eli-mcp

Claude Code:

claude mcp add pk-eli-mcp -- uvx pk-eli-mcp

Or drop .mcp.json.example into your project as .mcp.json.

Windows 11 with Smart App Control

Smart App Control blocks unsigned executables, which covers uvx.exe, pip.exe and the pk-eli-mcp.exe launcher that pip writes at install time. The python.exe and py.exe from the python.org installer are signed by the Python Software Foundation, so running the module through the interpreter works:

python -m pip install pk-eli-mcp
python -m pk_eli_mcp

pip.exe is blocked for the same reason, so install with python -m pip, not pip install. If python is not on PATH, use the Windows launcher: py -3 -m pk_eli_mcp.

{ "mcpServers": { "pk-eli-mcp": { "command": "python", "args": ["-m", "pk_eli_mcp"] } } }

Do not turn Smart App Control off to work around this - it cannot be re-enabled without reinstalling Windows.

Configuration

Env

Default

Purpose

PK_ELI_CACHE_DIR

~/.matematic/cache/pk-eli

Corpus file + HTTP cache

PK_ELI_AUDIT_DIR

~/.matematic/audit

JSONL audit log (one line per tool call)

PK_ELI_CORPUS_URL

the pk-laws-corpus.json.gz asset of this repository's latest GitHub release

Statute corpus mirror; '' skips it and downloads the pinned Hugging Face revision directly (the Claude plugin does this)

Network: statute searches run on the local corpus; judgment searches send the query to Hugging Face's public datasets-server. The corpus is downloaded once, from the mirror above or from Hugging Face. No LLM provider, no telemetry.

Development

python -m venv .venv && .venv/Scripts/pip install -e ".[dev]"   # Linux/macOS: .venv/bin/pip
ruff check src tests
pytest tests/test_instructions_drift.py tests/test_corpus.py   # offline
pytest tests/test_smoke.py                                     # live (downloads the corpus)

Governance

Read-only by design: the server can search and fetch, never write. Every tool call appends an audit line (~/.matematic/audit/pk-eli-mcp.jsonl) with a SHA-256 input hash, duration and status. See CONSTITUTION.md for the rules this connector is built under and DISCOVERY.md for how the sources were chosen.

License

Apache-2.0 for this code. The datasets keep their own licenses (ODC-BY 1.0 and MIT); the underlying texts are Government of Pakistan public legal documents.

Available Tools

6 tools
pk_coverageA
Read-onlyIdempotent

Declare what this connector covers, how it is sourced, and what it does NOT cover.

Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead.

Returns: Coverage with families, an as-of note, and a non-empty list of known gaps.

Inputs: no named parameters. Returns: What this connector covers, how it is sourced, and what it does not cover.

pk_get_decisionA
Read-onlyIdempotent

Fetch one Supreme Court judgment's full text, by row index or registry citation.

Inputs: case_id, row_idx. Returns: Result of ``pk_get_decision`` - the full text of one judgment.

pk_get_lawA
Read-onlyIdempotent

Fetch the full text of one federal statute. Large statutes are truncated.

Inputs: law_id (required). Returns: Result of ``pk_get_law`` - the full text of a statute, possibly truncated.

pk_search_lawsA
Read-onlyIdempotent

Keyword search over Pakistan's 967 federal statutes (title-weighted ranking).

Inputs: query (required), limit. Returns: Result of ``pk_search_laws``.

pk_verify_citationsA
Read-onlyIdempotent

Verify Pakistani legal citations found in a text against the corpus.

Extracts statute sections ("section 302 of the Pakistan Penal Code", "section 10A of the Pakistan Study Centres Act, 1976"), act coordinates ("Act No. XLV of 1860"), Constitution articles ("Article 184(3) of the Constitution") and Supreme Court registry citations ("Crl.A. 93/2013"), then checks each against the local corpus. A parenthetical description right after a citation is content-checked with a trigram match (mismatch = review signal). Non-existent sections come back with a range hint of what DOES exist.

Inputs: text (required), max_citations. Returns: Result of ``pk_verify_citations``.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct operation: statute search, statute retrieval, case search, case retrieval, coverage disclosure, and citation verification. The search/get pairs are clearly separated by corpus, and pk_verify_citations has a specialized purpose that does not overlap with the plain search tools.

    Naming Consistency3/5

    Most tools follow a pk_ + verb_noun pattern such as pk_search_laws and pk_get_decision, but pk_case_search reverses the order and pk_coverage is a bare noun rather than a verb phrase. The pk_ prefix provides some consistency, but the naming conventions are mixed overall.

    Tool Count5/5

    Six tools is well-scoped for a legal research connector: two search/retrieve pairs cover the two corpora, plus coverage and citation verification add necessary meta-capabilities. Each tool earns its place and none feel redundant.

    Completeness4/5

    The set covers search and retrieval for both federal statutes and Supreme Court judgments, plus citation verification and explicit gap disclosure, which is strong for a read-only legal corpus. The main limitation is that large statutes are truncated with no continuation mechanism, and case retrieval relies on row index or registry citation rather than broader citation formats.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server providing AI assistants access to Canadian case law and legislation metadata from CanLII across all jurisdictions, supporting search and citation relationships.
      7
      32 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server to search and retrieve passages from a corpus of 7,872 classical Islamic books via the Sahifah API, with full citations and mu'tabar filtering.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Azerbaijan's official legal-acts database (e-qanun.az), enabling search, metadata retrieval, and full-text access to legislative and judicial documents.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for U.S. federal law that enables searching the U.S. Code, CFR, Federal Register, case law, and bills, with citation verification against primary sources to prevent hallucinations.
      11
      MIT