Indian Legal MCP
REMOTE · GSMS-B-INDIAN-LEGAL-MCP.HF.SPACE · SCANNED SEP 27
Structured access to 10 major Indian legal texts (BNS, IPC, etc) for AI agents.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability90
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 816 tokens (~102/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Indian Legal MCP server?
Indian Legal MCP is a hosted endpoint at https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gsms-b-indian-legal-mcp.hf.space
claude mcp add --transport http gsms-b-indian-legal-mcp 'https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/'
{
"mcpServers": {
"gsms-b-indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/"
}
}
} {
"servers": {
"gsms-b-indian-legal-mcp": {
"type": "http",
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/"
}
}
} [mcp_servers.gsms-b-indian-legal-mcp] url = "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gsms-b-indian-legal-mcp": {
"type": "remote",
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/",
"enabled": true
}
}
} openclaw mcp add gsms-b-indian-legal-mcp --url 'https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/' --transport streamable-http
mcp_servers:
gsms-b-indian-legal-mcp:
url: "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/" {
"McpServers": {
"gsms-b-indian-legal-mcp": {
"Transport": "http",
"Url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/"
}
}
} assistant mcp add gsms-b-indian-legal-mcp -t streamable-http -u 'https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/'
{
"mcpServers": {
"gsms-b-indian-legal-mcp": {
"type": "http",
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- Tool “indian_legal_mcp_get_section” rewrote its description, which is the text the model reads security
- Tool “indian_legal_mcp_search_keyword” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: 100 functional
- New prompt “indian_legal_mcp_analyze_factual_scenario” functional
- New prompt “indian_legal_mcp_breakdown_legal_ingredients” functional
- New prompt “indian_legal_mcp_compare_old_and_new_law” functional
- New prompt “indian_legal_mcp_create_law_student_study_note” functional
- New prompt “indian_legal_mcp_draft_lawyer_quick_brief” functional
- New prompt “indian_legal_mcp_draft_legal_research_note” functional
- New prompt “indian_legal_mcp_explain_legal_terms” functional
- New prompt “indian_legal_mcp_explain_to_beginner” functional
- New prompt “indian_legal_mcp_explain_to_client” functional
- New prompt “indian_legal_mcp_find_relevant_sections” functional
- New prompt “indian_legal_mcp_missing_information_checklist” functional
- New prompt “indian_legal_mcp_preliminary_legal_research” functional
- New prompt “indian_legal_mcp_summarize_statutory_changes” functional
- New prompt “indian_legal_mcp_trace_concept_across_acts” functional
- New prompt “indian_legal_mcp_verify_legal_claim” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hf.space | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 27 Sept 2026 | 12 Apr 2027 | RSA 2048 | SHA256-RSA | f51719dcdf7239b73ac39d3e38d8e9d |
| SANs: hf.space, *.hf.space | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gsms-b-indian-legal-mcp.hf.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| space. | present | 51168 | 13 | Verified |
| hf.space. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/ | Verified | 200 | |
| http (plaintext) | http://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/ | HTTPS enforced | 301 | https://gsms-b-indian-legal-mcp.hf.space:443/gradio_api/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
indian_legal_mcp_get_act_info ~86
Get metadata about one specific Act: its full name, year enacted, and whether it is still current law or has been repealed and replaced by something newer.
| Name | Type | Req | Description |
|---|---|---|---|
| act_code | string | yes | short code, one of BNS, BNSS, BSA, IPC, CRPC, IEA, COI, CPC, MVA, NIA. |
No output schema declared.
No examples provided.
indian_legal_mcp_get_chapter ~106
Get every section within one chapter of an Act, with full text. Only meaningful for BNS, BNSS, BSA, IPC, CRPC, IEA. For CPC, MVA, and COI, which lack chapter grouping in this dataset, it returns a clear message instead of empty data.
| Name | Type | Req | Description |
|---|---|---|---|
| act_code | string | yes | e.g. 'BNS'. |
| chapter_number | string | yes | e.g. '1', '16'. |
No output schema declared.
No examples provided.
indian_legal_mcp_get_full_act ~91
Get an entire Act, in full, returned in paginated chunks (50 sections/page). Use only when genuinely needing the whole Act. If a page beyond the total pages is requested, it gracefully returns empty sections with a note.
| Name | Type | Req | Description |
|---|---|---|---|
| act_code | string | yes | e.g. 'BNS'. |
| page | integer | – | The page number to fetch. Default is 1. |
No output schema declared.
No examples provided.
indian_legal_mcp_get_section ~187
[AI TOOL ORCHESTRATION INSTRUCTION: Only use this tool AFTER you have found the exact section number via search_keyword, or if the user explicitly provided it.] Get the exact text of ONE section (or Constitution article) by its number. Use this when someone asks about a specific, known section number, e.g. 'what does BNS Section 103 say' or 'show me IPC 302'. If the Act is repealed (IPC, CRPC, or IEA), the result includes a note that it no longer applies to new cases and names what replaced it.
| Name | Type | Req | Description |
|---|---|---|---|
| act_code | string | yes | e.g. 'BNS', 'IPC', 'COI'. |
| section_number | string | yes | e.g. '103', '25A', '0' (Preamble), '394A'. Always given as a string. |
No output schema declared.
No examples provided.
indian_legal_mcp_get_section_range ~107
Get all sections between a start and end number (inclusive) with full text. Numeric comparison handles letter-suffixed numbers (like '108A'). If start and end are provided in reverse order, it silently corrects them and includes a note in the response.
| Name | Type | Req | Description |
|---|---|---|---|
| act_code | string | yes | e.g. 'BNS'. |
| end_section | string | yes | e.g. '110'. |
| start_section | string | yes | e.g. '100'. |
No output schema declared.
No examples provided.
indian_legal_mcp_list_acts ~41
List all available Acts in the database, with metadata and descriptions. Use this to see which legal codes are supported or find short codes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
indian_legal_mcp_list_sections ~75
List every section NUMBER and TITLE in one Act, without the full body text. Use this to browse what exists in an Act before deciding which specific section or chapter to fetch in full -- much shorter than get_full_act.
| Name | Type | Req | Description |
|---|---|---|---|
| act_code | string | yes | e.g. 'BNS', 'MVA'. |
No output schema declared.
No examples provided.
indian_legal_mcp_search_keyword ~123
[AI TOOL ORCHESTRATION INSTRUCTION: ALWAYS use this tool FIRST when the specific section number is unknown. Never guess section numbers.] Search section titles and text. Exact title matches are ranked #1, partial title matches are #2, and body text matches are #3 (via BM25). This is exact/near-exact word matching, NOT meaning-based search.
| Name | Type | Req | Description |
|---|---|---|---|
| act_code | string | – | optional -- restrict search to one Act. |
| query | string | yes | search term(s), e.g. 'punishment for murder'. |
No output schema declared.
No examples provided.
What is the Indian Legal MCP server?
Indian Legal MCP is listed in the public MCP registry as io.github.GSMS-B/indian-legal-mcp. Structured access to 10 major Indian legal texts (BNS, IPC, etc) for AI agents. This page covers its hosted endpoint (https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/).
Is the Indian Legal MCP server safe to use?
Indian Legal MCP scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Indian Legal MCP server expose?
Indian Legal MCP exposes 8 tools: indian_legal_mcp_list_acts, indian_legal_mcp_get_act_info, indian_legal_mcp_get_section, indian_legal_mcp_list_sections, indian_legal_mcp_get_chapter, and 3 more. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.
Does the Indian Legal MCP server require authentication?
No. We connected to Indian Legal MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Indian Legal MCP server still maintained?
Indian Legal MCP is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.