Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LegalSearch

REMOTE · MCP.ROOPSLAW.AI

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

Available components

0 this week 74 Trust /100

Last scanned (13 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 319 tokens (~53/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 19% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Stability: 0.97 → pass security
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.roopslaw.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.roopslaw.ai CN=YE2,O=Let's Encrypt,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA384 686e18b0bcf51af3371908cb89f67f202d4
SANs: mcp.roopslaw.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.roopslaw.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
roopslaw.ai. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.roopslaw.ai/mcp Verified 200
http (plaintext) http://mcp.roopslaw.ai/mcp HTTPS enforced 308 https://mcp.roopslaw.ai/mcp
MCP tools · 6 exposed · ~319 tokens

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 →

Tool Tokens
roop.public.corpus.status ~24

Report the public corpus surfaces exposed through this DMZ MCP.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

roop.public.judgments.get_packet ~38

Fetch a bounded public judgment or appellate tribunal packet by ROOP judgment id.

NameTypeReqDescription
roop_idstringyes–

No output schema declared.

No examples provided.

roop.public.judgments.get_segment ~56

Fetch one bounded, continuable segment of an exact public judgment by ROOP judgment id.

NameTypeReqDescription
max_charsinteger––
offsetinteger––
roop_idstringyes–

No output schema declared.

No examples provided.

roop.public.judgments.search ~63

Search public Indian judgment and appellate tribunal metadata plus public snippets.

NameTypeReqDescription
courtstring–Optional public court or tribunal code such as SC, DELHC, or NCLAT.
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

roop.public.statutes.get_packet ~40

Fetch a bounded public statute packet using the public statutes search surface.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

roop.public.statutes.search ~98

Search public statutes and subordinate legislation metadata.

NameTypeReqDescription
doc_kindstring––
instrumentTypestring–Camel-case alias for instrument_type.
instrument_typestring–Optional instrument type filter such as rules, regulations, notification, order, circular, or form.
jurisdiction_scopestring––
limitinteger––
querystringyes–
state_codestring––

No output schema declared.

No examples provided.

Install

How do I install the LegalSearch MCP server?

LegalSearch is a hosted endpoint at https://mcp.roopslaw.ai/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 · mcp.roopslaw.ai

# add to Claude Code
claude mcp add --transport http ai-roopslaw-legalsearch 'https://mcp.roopslaw.ai/mcp'
Common questions

What is the LegalSearch MCP server?

LegalSearch is an MCP server listed in the public MCP registry as ai.roopslaw/legalsearch. Public Indian legal search MCP for Roop judgments, statutes, and corpus grounding. This page covers its hosted endpoint (https://mcp.roopslaw.ai/mcp).

Is the LegalSearch MCP server safe to use?

LegalSearch scores 74 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 LegalSearch MCP server expose?

LegalSearch exposes 6 tools: roop.public.judgments.search, roop.public.judgments.get_packet, roop.public.judgments.get_segment, roop.public.statutes.search, roop.public.statutes.get_packet, roop.public.corpus.status. Their descriptions and schemas cost roughly 319 tokens of context every time the server is loaded.

Does the LegalSearch MCP server require authentication?

No. We connected to LegalSearch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LegalSearch MCP server still maintained?

LegalSearch is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the LegalSearch MCP server?

VerifyMCP ran 12 checks on LegalSearch, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about LegalSearch: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.