MCP.so
Sign In

Descrybe Legal Engine MCP Server

@Descrybe Legal Engine

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Other

Author

Descrybe Legal Engine

About Descrybe Legal Engine MCP Server

Descrybe Legal Engine provides structured U.S. primary-law context for legal work. Its connector helps assistants ground legal research in clean source material, supporting searches, summaries, and analysis across U.S. legal documents.

Connection details

https://mcp.descrybe.com/mcp

Setup

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

Descrybe Legal Engine MCP Server tools

13

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

Frequently asked questions

1

What is the Descrybe Legal Engine remote MCP server?

The Descrybe Legal Engine remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.descrybe.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Descrybe Legal Engine MCP server?

Add the endpoint https://mcp.descrybe.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Descrybe Legal Engine MCP server require authentication?

Yes. Descrybe Legal Engine uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the Descrybe Legal Engine MCP server use?

Descrybe Legal Engine exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments