Is the Roopslaw Legalsearch MCP server down?

mcp-registry/ai.roopslaw/legalsearch · v0.2.0

Also listed as glama/roop-world/legalsearch

grade A

healthy

Last checked 2026-10-26 18:25 UTC · handshake 818ms

As of 2026-10-26 18:25 UTC, the Roopslaw Legalsearch MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)

100%

checks observed

4,903

outages (90d)

tools

Public Indian legal search MCP for Roop judgments, statutes, and corpus grounding.

Point your MCP client at this streamable-http endpoint: https://mcp.roopslaw.ai/mcp

Agent-readiness: D (61/100)

grade D

D (61/100): 0 error(s), 4 warning(s) across 6 tool(s); ~637 tokens of tool definitions.

Scores higher than 0% of 15,767 MCP servers Glimind has audited.

Its tool list costs an agent ~637 tokens per session — lighter than 85% of servers.

59 → 59 since 2026-10-17

no tool-poisoning patterns

Schemas100

Descriptions32

Safety hints30

Token cost100

Client compatibility20

Protocol40

Reliability100

Stability100

What to fix (5)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: roop.public.corpus.status, roop.public.judgments.get_packet, roop.public.judgments.get_segment, roop.public.judgments.search, roop.public.statutes.get_packet and 1 more

6 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: roop.public.corpus.status, roop.public.judgments.get_packet, roop.public.judgments.get_segment, roop.public.judgments.search, roop.public.statutes.get_packet and 1 more

13 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: roop.public.judgments.get_packet, roop.public.judgments.get_segment, roop.public.judgments.search, roop.public.statutes.get_packet, roop.public.statutes.search

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.roopslaw%2Flegalsearch/fixes

roop.public.corpus.status 2 changes

Renamed "roop.public.corpus.status" → "roop_public_corpus_status" (letters, digits, _ and - only; max 64). Keep the old name as an alias for a release if clients already call it. (verify)
Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "roop_public_corpus_status",
  "description": "Report the public corpus surfaces exposed through this DMZ MCP.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

roop.public.judgments.get_packet 2 changes

Renamed "roop.public.judgments.get_packet" → "roop_public_judgments_get_packet" (letters, digits, _ and - only; max 64). Keep the old name as an alias for a release if clients already call it. (verify)
Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "roop_public_judgments_get_packet",
  "description": "Fetch a bounded public judgment or appellate tribunal packet by ROOP judgment id.",
  "inputSchema": {
    "type": "object",
    "required": [
      "roop_id"
    ],
    "properties": {
      "roop_id": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

roop.public.judgments.get_segment 2 changes

Renamed "roop.public.judgments.get_segment" → "roop_public_judgments_get_segment" (letters, digits, _ and - only; max 64). Keep the old name as an alias for a release if clients already call it. (verify)
Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "roop_public_judgments_get_segment",
  "description": "Fetch one bounded, continuable segment of an exact public judgment by ROOP judgment id.",
  "inputSchema": {
    "type": "object",
    "required": [
      "roop_id"
    ],
    "properties": {
      "offset": {
        "type": "integer",
        "maximum": 2000000,
        "minimum": 0
      },
      "roop_id": {
        "type": "string"
      },
      "max_chars": {
        "type": "integer",
        "maximum": 20000,
        "minimum": 1000
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.roopslaw/legalsearch"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.roopslaw/legalsearch"}) over MCP.

Passed

Every tool has a well-formed, typed input schema.
No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
Compact tool list (~637 tokens).
99.98% uptime over 30 days.
No breaking contract changes in 30 days.

Largest tool definitions

roop.public.statutes.search ~193 tokens
roop.public.judgments.search ~118 tokens
roop.public.judgments.get_segment ~110 tokens
roop.public.statutes.get_packet ~87 tokens
roop.public.judgments.get_packet ~75 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.roopslaw%2Flegalsearch.svg)](https://glimind.com/server/mcp-registry%2Fai.roopslaw%2Flegalsearch?ref=badge)

HTML

<a href="https://glimind.com/server/mcp-registry%2Fai.roopslaw%2Flegalsearch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.roopslaw%2Flegalsearch.svg" alt="MCP agent-readiness"></a>

reStructuredText

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.roopslaw%2Flegalsearch.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.roopslaw%2Flegalsearch?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5c391e698cd02d55…, first seen 2026-10-17, included at leaf 5203 of 74,700. Version history · verify what your client received.

Tools (6)

Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Roopslaw Legalsearch MCP server down right now?

How many tools does Roopslaw Legalsearch MCP server provide?

Roopslaw Legalsearch MCP server advertises 6 tools, including roop.public.corpus.status, roop.public.judgments.get_packet, roop.public.judgments.get_segment, roop.public.judgments.search, roop.public.statutes.get_packet.

How do I install Roopslaw Legalsearch MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.roopslaw.ai/mcp

Is the Roopslaw Legalsearch MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Roopslaw Legalsearch MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.