Home / MCP registry index / io.github.GSMS-B/indian-legal-mcp
Indian Legal MCP
io.github.GSMS-B/indian-legal-mcp in the official MCP registry.
Endpoint https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/. Source: github.com/GSMS-B/indian-legal-mcp.
The registry describes it as: Access 102 Indian Acts, 2026 Constitution, criminal mappings, and 10 legal research skills.
We read its 16 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
indian_legal_mcp_list_acts indian_legal_mcp_get_act_info indian_legal_mcp_resolve_act indian_legal_mcp_get_section indian_legal_mcp_list_sections indian_legal_mcp_get_chapter indian_legal_mcp_get_section_range indian_legal_mcp_get_full_act indian_legal_mcp_search_keyword indian_legal_mcp_convert_section indian_legal_mcp_get_constitution_schedule indian_legal_mcp_list_constitution_schedules indian_legal_mcp_get_constitution_appendix indian_legal_mcp_list_constitution_appendices indian_legal_mcp_list_skills indian_legal_mcp_get_skill
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-gsms-b-indian-legal-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.