Back to MCP servers

Indian-Legal-MCP

https://server.smithery.ai/gsms-b/Indian-Legal-MCP/mcp
● healthy

# Indian Legal MCP: The Definitive Legal Protocol for AI Agents The Indian Legal MCP Server provides AI agents with high-speed, structured, and strictly sourced access to the 10 major Indian legal texts. Designed specifically to eliminate AI hallucinations in legal research, this tool connects LLMs directly to an authoritative SQLite database, ensuring that every legal response is grounded in exact, verifiable statutory text. ### Supported Legal Texts (Current & Repealed) * **BNS** (Bharatiya Nyaya Sanhita, 2023) * **BNSS** (Bharatiya Nagarik Suraksha Sanhita, 2023) * **BSA** (Bharatiya Sakshya Adhiniyam, 2023) * **IPC** (Indian Penal Code, 1860 - Repealed) * **CrPC** (Code of Criminal Procedure, 1973 - Repealed) * **IEA** (Indian Evidence Act, 1872 - Repealed) * **COI** (Constitution of India) * **CPC** (Code of Civil Procedure, 1908) * **MVA** (Motor Vehicles Act, 1988) * **NIA** (Negotiable Instruments Act, 1881) ### Key Features for AI Agents 1. **Precision Keyword Search:** Utilizes exact/BM25 lexical matching to find specific legal terminology without relying on semantic guesswork. 2. **Context-Aware Fetching:** Agents can fetch specific chapters, individual sections, or exact section ranges to prevent blowing out their context windows. 3. **Repeal Awareness:** Automatically detects when an agent queries repealed laws (like the IPC or CrPC) and attaches mandatory structural notes guiding the AI to the modern replacements (BNS, BNSS). 4. **Smart Pagination:** Built-in safeguards allow agents to read entire acts in 50-section paginated chunks without crashing. ### Why use this MCP? Standard AI models guess what the law says based on training data. By equipping your agent with the Indian Legal MCP, it transforms from a predictive text engine into a precise legal researcher that cites exact section numbers, respects historical legal transitions, and delivers uncompromised accuracy for the Indian judicial system.

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 81/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 23/25 Endpoint answers the MCP initialize handshake (6029 ms); very slow response -2.
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 16 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Very slow (6029 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 52% of peers
This listing 81 · peer median 81
Latency
Faster than 21% of peers
This listing 613 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days.
  • Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/gsms-b/Indian-Legal-MCP/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/gsms-b/Indian-Legal-MCP/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://smithery.ai/servers/gsms-b/Indian-Legal-MCP
Listed at (smithery)
https://smithery.ai/servers/gsms-b/Indian-Legal-MCP