Lipe Court Record
by dalenz50010 · remote · no sign-in to list tools · v0.3.0 · published by GitHub user dalenz50010
Search page-cited evidence from the public court record in Lipe v. Lupus Superior.
7 tools: 7 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things0Claude Code: ask
- Only reads7Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http lipe-court-record https://lipe-api-production.up.railway.app/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
7 tools
Only reads 7Claude Code: allow
fetchFetch one search result's exact physical PDF page, reviewed evidence, provenance, and permanent citation URL.No findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
Description, as the server wrote it Fetch one search result's exact physical PDF page, reviewed evidence, provenance, and permanent citation URL. Use the returned classification and filename/page citation in the answer.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_case_overviewReturn a concise, reviewed orientation to one case with evidence classifications and page citations.No findings
Why it is in this group
- The name "get_case_overview" says "get": a word for reading.
Description, as the server wrote it Return a concise, reviewed orientation to one case with evidence classifications and page citations. Use for first-time users, then search and fetch before answering detailed questions. `case` is a case id from list_cases.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
grepFind every page whose extracted text contains an exact phrase, whole word or regular expression - for a quotation, a dollar figure, a cause or exhibit number, a name or a defined t…No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it Find every page whose extracted text contains an exact phrase, whole word or regular expression - for a quotation, a dollar figure, a cause or exhibit number, a name or a defined term, where search ranks by meaning and may miss the exact words. Returns the total count, counts per filing, and each match's page id, citation and snippet. Case-insensitive unless case_sensitive; curly quotes, dashes, ligatures and line breaks are normalized. `document` filters by filename substring. Matches are automatically extracted text, not verified: fetch the page before quoting it. Zero matches means zero in the extracted text, not that the record lacks the words.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
list_case_topicsList the evidence topics covered for one case and suggested questions.No findings
Why it is in this group
- The name "list_case_topics" says "list": a word for reading.
Description, as the server wrote it List the evidence topics covered for one case and suggested questions. Use when the user asks what the connector knows or what they should investigate. `case` is a case id from list_cases.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
list_casesList the court cases this connector holds: id, caption, cause number, court, status and the incident each concerns.No findings
Why it is in this group
- The name "list_cases" says "list": a word for reading.
Description, as the server wrote it List the court cases this connector holds: id, caption, cause number, court, status and the incident each concerns. Pass an id as `case` to search, get_case_overview, list_case_topics and list_record_limitations. Every page id returned by search names its case.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
list_record_limitationsList what one case's reviewed record does NOT establish: unavailable filings, facts the evidence does not verify, review scope, and the legal status a document can and cannot prove…No findings
Why it is in this group
- The name "list_record_limitations" says "list": a word for reading.
Description, as the server wrote it List what one case's reviewed record does NOT establish: unavailable filings, facts the evidence does not verify, review scope, and the legal status a document can and cannot prove. Call before asserting the record establishes something, and before answering a question the search results do not squarely answer. `case` is a case id from list_cases.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
searchSearch the court record for case facts, testimony, positions, rulings, and jury findings.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search the court record for case facts, testimony, positions, rulings, and jury findings. Call this for every case-specific factual question, then call fetch on relevant result IDs before answering. Each result says whether the page is in the reviewed evidence ledger and which classification it carries, so prefer reviewed pages over automatically extracted ones when both answer the question. `case` confines the search to one case id from list_cases; it is required once more than one case is held.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http lipe-court-record https://lipe-api-production.up.railway.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lipe-court-record__list_cases",
"mcp__lipe-court-record__search",
"mcp__lipe-court-record__fetch",
"mcp__lipe-court-record__grep",
"mcp__lipe-court-record__get_case_overview",
"mcp__lipe-court-record__list_case_topics",
"mcp__lipe-court-record__list_record_limitations"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as lipe-court-record. Review it before you use it.