Lipe Court Record MCP Server

by dalenz50010 Your server? Claim it

answering

Lipe Court Record is answering right now. Last checked 1 min ago. It exposes 6 tools.

Search page-cited evidence from the public court record in Lipe v. Lupus Superior.

Uptime history 8 days of history · worst day 97%

8 days agonow

100.0%

Uptime 24h

93 of 93 checks

Tools

read from the server

300 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.

10 Sep 4 tool descriptions were rewritten get_case_overview, list_case_topics, list_record_limitations and 1 more

10 Sep 4 tools changed the parameters they ask for get_case_overview, list_case_topics, list_record_limitations and 1 more

10 Sep a tool appeared list_cases

8 Sep a tool appeared list_record_limitations

8 Sep a tool description was rewritten search

Nothing serious here today

Today is the operative word: we check Lipe Court Record every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add lipe-court-record --transport http https://lipe-api-production.up.railway.app/mcp

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

{
  "mcpServers": {
    "lipe-court-record": {
      "url": "https://lipe-api-production.up.railway.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.lipe-court-record]
url = "https://lipe-api-production.up.railway.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "lipe-court-record": {
      "url": "https://lipe-api-production.up.railway.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "lipe-court-record": {
      "url": "https://lipe-api-production.up.railway.app/mcp"
    }
  }
}

Available tools 6

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

case

get_case_overview

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.

list_case_topics

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.

cases

list_cases

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.

fetch

fetch

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.

record

list_record_limitations

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.

search

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.

Endpoints

URL	Transport	State	Latency	Checked
https://lipe-api-production.up.railway.app/mcp	streamable-http	answering	290 ms	1 min ago

Alternatives to Lipe Court Record

same job, measured the same way

Case Doha Record

by klmlfl

Search 30,000+ decided U.S. DOHA security-clearance decisions, cited to the public record.

7 tools answering

Atisbo Documentation

by brian8a1

Read-only search and page retrieval from the public Atisbo documentation corpus. No authentication.

3 tools answering

Loreboard

by loreboard

Search curated Lorcana resources, evidence, taxonomies, and public change history.

4 tools answering

Pubrecords

by bch1212

US public-records intelligence for AI agents — companies, SEC, courts, spending, licenses.

10 tools answering

Solution Commons

by carbaj03

Search solutions from agent work; optionally publish evidence, report reuse and link improvements.

5 tools answering

Vagus Lab Research

by vaguslab

Cited VNS research passages from a curated corpus, plus a scored device comparison.

3 tools answering

Crawdar Business Research

by crawdar

Evidence-backed public business research for agents with compact, pageable output.

10 tools answering

searchcode

by searchcode

Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.

6 tools answering

Lipe Court Record — questions

Answers built from our own checks of this server.

What can Lipe Court Record do?

It exposes 6 tools, read directly from the server on our last check. Among them: fetch, get_case_overview, list_cases, list_case_topics, list_record_limitations, search. 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 →

Is Lipe Court Record working right now?

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

How do I connect Lipe Court Record?

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 Lipe Court Record need an API key?

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

How fast is Lipe Court Record?

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