Descrybe Legal Engine MCP Server

vendor.descrybe-legal-engine/mcp

answering

Descrybe Legal Engine is answering right now. Last checked 7 min ago. It exposes 13 tools.

Uptime history 29 hours of history

29 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

299 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.descrybe.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.descrybe.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.descrybe.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.descrybe.com/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

case

check_case_status

Checks a known Descrybe case for a quick treatment/status signal before relying on it. Requires a Descrybe case_id. Returns whether later cases appear to treat the case positively, negatively, cautiously, or neutrally, plus a rough authority-weight label. This is a fast status check, not a full citing-case map and not a forum-specific binding analysis.

find_case_from_reference

Resolves a citation, case name, case caption, party name, party-name variant, docket number, short cite, quote, or mixed reference into a Descrybe case or candidate set. Use this for party-name or docket-number case lookup when the user does not already have a Descrybe case_id. Resolved cases and candidates include case_id, the Descrybe canonical identifier accepted by known-case tools. The context_text field can improve short, bare, or ambiguous references.

get_case_details

Retrieves case metadata, summary availability, opinion inventory, and treatment summary for a known Descrybe case. Requires a Descrybe case_id.

get_case_passages

Returns a small ranked list of focused raw passages from a known Descrybe case's primary opinion. Requires a Descrybe case_id and a focus issue, phrase, rule, quote, or fact pattern. This is not a full-opinion fetch and does not return every occurrence.

get_case_pdf

Creates or reuses a generated Descrybe case PDF asset and returns its public URL. Requires a Descrybe case_id. Returns URL/job metadata or preparation status, not PDF bytes; present the URL to the user instead of trying to download the file.

get_case_summary

Retrieves the precomputed standard or simplified summary for a known Descrybe case's primary opinion. Requires a Descrybe case_id; for legal research, prefer the standard summary unless the user asks for a simplified or plain-language explanation.

search_case_text

Searches the full text of judicial opinions by exact words or phrases across Descrybe's case-law text index. Useful when specific language matters, such as terms of art, quotes, statutory phrases, or uncommon factual wording. Each result includes case_id, the Descrybe canonical identifier accepted by known-case tools.

cases

find_cases_that_cite

Finds later cases that cite a known Descrybe case. Requires a Descrybe case_id. Useful for updating research, finding treatment, or locating newer authority that follows, distinguishes, or discusses the case. Returned citing cases include case_id when a Descrybe case is identified.

search_cases_by_concept

Use this first when the user wants to find leading or relevant cases about a legal issue, doctrine, fact pattern, jurisdiction, claim, defense, or topic and does not already have a Descrybe case_id. Results are authority-ranked by default to surface stronger legal authorities before ordinary text matches. Use date sorting only when the user asks for recent or newest cases. Each result includes case_id, the Descrybe canonical identifier accepted by known-case tools.

analyze

analyze_legal_question

Assess a broad or fact-dependent legal research question before searching to identify the jurisdiction, facts, legal issue, and procedural context needed for useful research. Returns ready_for_research or needs_clarification with up to three short clarifying questions.

extract

extract_case_references

Extracts case-law citations and references from legal text provided in the text argument. Returns one item per unique resolved case or best unresolved reference cluster, with occurrence counts, raw citations seen, and tagged excerpts. When resolve=true, results include compact case-identity resolution and a quick treatment indicator for each resolved case, including case_id when a Descrybe case is resolved. This does not verify quotes, analyze support, or return a full citing-case treatment map.

laws

search_laws_and_rules

Semantic/concept search over U.S. non-case primary law, including statutes, regulations, and constitutional provisions. Useful for legal rules outside judicial opinions when the issue, rule, citation, or topic can be described in natural language. Results are ranked by concept similarity and returned with compact matched source passages.

verify

verify_quote

Verifies whether quoted language appears in a known Descrybe case and locates the matching opinion. Requires a Descrybe case_id and exact or near-exact quote text. Returns whether the quote was found, where it matched, and which opinion contained it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.descrybe.com/mcp	streamable-http	answering	215 ms	7 min ago

Descrybe Legal Engine — questions

Answers built from our own checks of this server.

What can Descrybe Legal Engine do?

It exposes 13 tools, read directly from the server on our last check. Among them: analyze_legal_question, check_case_status, extract_case_references, find_case_from_reference, find_cases_that_cite, get_case_details and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Descrybe Legal Engine mostly used for?

Its tools cluster around case and cases. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Descrybe Legal Engine working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 299 ms. The bar chart above shows every period we have measured.

How do I connect Descrybe Legal Engine?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Descrybe Legal Engine need an API key?

No. Descrybe Legal Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Descrybe Legal Engine?

It answers our handshake in 299 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.