Indian Legal MCP
by gsms-bco.huggingface.gsms-b/indian-legal-mcp
- Remote endpoint
- 32 tools
- MIT
Uptime
Checked · every day
100%from 5 days of checks
Up without downtime on 4 of 4 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 998 ms, slowest 5% 1114 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
16 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No verdict yet | 0 | – |
| 2 Nov | No downtime | 1of 1 | 999 ms |
| 1 Nov | No downtime | 1of 1 | 1073 ms |
| 31 Oct | No downtime | 1of 1 | 1065 ms |
| 30 Oct | No downtime | 1 | 989 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse indian-legal-mcp https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"indian-legal-mcp": {
"type": "sse",
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"indian-legal-mcp": {
"type": "sse",
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "indian-legal-mcp"
type: sse
url: "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"indian-legal-mcp":
type: streamable_http
name: "indian-legal-mcp"
enabled: true
uri: "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add indian-legal-mcp --url https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Indian Legal MCP (`co.huggingface.gsms-b/indian-legal-mcp`)
Its page: https://plug.directory/servers/co.huggingface.gsms-b/indian-legal-mcp
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse indian-legal-mcp https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"indian-legal-mcp": {
"type": "sse",
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"indian-legal-mcp": {
"type": "sse",
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "indian-legal-mcp"
type: sse
url: "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"indian-legal-mcp": {
"url": "https://gsms-b-indian-legal-mcp.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 32
indian_legal_mcp_analyze_factual_scenarioAnalyze a user's fact pattern and explain how the law applies.indian_legal_mcp_breakdown_legal_ingredientsExtract and list the constituent legal elements (ingredients) of a section.indian_legal_mcp_compare_old_and_new_lawCompare an old repealed law (e.g., IPC) with its modern equivalent (e.g., BNS).indian_legal_mcp_convert_sectionMap/convert any criminal law section between the old repealed codes (IPC, CrPC, IEA) and the new 2023 criminal codes (BNS, BNSS, BSA) in either direction. Returns the corresponding section number, amendment status ('Retained', 'Change', 'Deleted', 'New Section', 'New Sub-Section'), a concise mapping statement, and the full statutory text of both sections for instant comparison. Examples: convert_section('IPC', '302') -> maps to BNS Section 103 (Punishment for murder) convert_section('BNS', '103') -> maps to IPC Section 302 + highlights new sub-section 103(2) (Mob Lynching) convert_section('CRPC', '437') -> maps to BNSS Section 480 (Non-bailable offence bail) convert_section('IEA', '65B') -> maps to BSA Section 63 (Electronic records admissibility) convert_section('IPC', '377') -> notes that this section was repealed and deleted in BNS convert_section('BNS', '111') -> notes that Organised Crime is a newly introduced provisionindian_legal_mcp_create_law_student_study_noteTurn a legal provision into a structured study note for exam revision.indian_legal_mcp_draft_lawyer_quick_briefProduce a concise, lawyer-oriented brief on a specific topic.indian_legal_mcp_draft_legal_research_notePrepare a structured preliminary legal research note for a given issue.indian_legal_mcp_explain_legal_termsIdentify and explain the difficult technical legal terms in a specific section.indian_legal_mcp_explain_to_beginnerExplain a specific legal section using simple, non-legal language for ordinary citizens.indian_legal_mcp_explain_to_clientConvert legal analysis of a situation into a client-friendly explanation.indian_legal_mcp_find_relevant_sectionsDetermine which statutory provisions apply to the given facts.indian_legal_mcp_get_act_infoGet 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.
From Hugging Face Spaces. Report a problem