ecourts-mcp-server
Connects LLMs to the EcourtsIndia Partner API for searching Indian court cases, retrieving orders, reading cause lists, and accessing AI summaries.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
rithik-cmyk
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
ecourts_get_caseRetrieve comprehensive details for an Indian court case by CNR (Case Number Record). Returns: case status, parties (petitioners/respondents), advocates, judges, hearing history, listing dates, judgment orders, interim orders, interlocutory applications, notices, filed documents, tagged/connected ma…
ecourts_search_casesSearch for Indian court cases with text queries, filters, date ranges, year filters, and faceted aggregations. Text search args (all optional): query, advocates, judges, petitioners, respondents, litigants Filter args (arrays): court_codes, case_types, case_statuses, judicial_sections, case_ca…
ecourts_get_orderGet metadata and download information for a court order PDF (certified true copy). Args: - cnr (string): Case Number Record - filename (string): Order filename obtained from judgmentOrders[].orderUrl or interimOrders[].orderUrl in the ecourts_get_case response Workflow: call ecourts_get_case →…
ecourts_get_order_aiGet extracted text and pre-computed AI analysis for a court order. AI analysis includes: summary, order type, outcome (PETITIONER_FAVORED, RESPONDENT_FAVORED, MIXED, DISMISSED), key points, relief granted, legal provisions cited, next steps, judge, and date. Args: - cnr (string): Case Number Rec…
ecourts_get_court_structureDiscover the Indian court hierarchy: State → District → Court Complex → Court. Use this to obtain valid codes for ecourts_search_cases (court_codes), ecourts_search_causelist, and ecourts_get_causelist_dates. Args: - level: "states" | "districts" | "complexes" | "courts" - state: required for …
ecourts_search_causelistSearch cause list entries across Indian courts. Args (at least one required): - q: full-text search (case numbers, parties, advocates) - date / start_date / end_date: date filters (YYYY-MM-DD) - bench: bench code filter - judge / advocate / litigant: name-based search - state / district_c…
ecourts_get_causelist_datesGet dates for which cause list data is available, filtered by location. At least one parameter is required: state, district_code, court_complex_code, or court_no. Free endpoint (no credit charge, authentication required). Use the returned dates with ecourts_search_causelist to avoid empty searches…
ecourts_refresh_caseRequest a fresh scrape of case data from the eCourts source. This is an asynchronous operation — the update takes 5-10 minutes. After refreshing, call ecourts_get_case to retrieve updated data. Duplicate requests within 15 minutes are idempotent (no double charge). Args: - cnr (string): Case Nu…
ecourts_lookup_caseFind a case using a human-readable case number (e.g. "CS(OS) 123/2024") instead of CNR. This is a convenience workflow: it searches for the case number, finds the matching CNR, and returns full case details in one step. Args: - case_number (string): Human-readable case number, e.g. "CS(OS) 123/2…
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`
axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge
ECOURTS_API_TOKENexport ="eci_live_your_token_here"TRANSPORTNo stdio (default) or httpPORTTool test coverage
Only 2/9 tools referenced in tests (22%)
Write tests that reference each tool by name so every tool has at least one test.
Production dependencies are patched
0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/rithik-cmyk/ecourts-mcp-server)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check