Lipe Court Record MCP Server

by dalenz50010 Your server? Claim it

not responding

Lipe Court Record is listed as active in the registry but did not answer our last check. It exposes 7 tools.

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

Uptime history 68 days of history · worst day 0%

68 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

187 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 12

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

5 Oct a tool appeared grep

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

Lipe Court Record does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "lipe-court-record": {
      "type": "http",
      "url": "https://lipe-api-production.up.railway.app/mcp"
    }
  }
}

Available tools 7

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.

grep

grep

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.

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	187 ms	8 min ago

Alternatives to Lipe Court Record

same job, measured the same way

The Parse

by theparse

Search a tiered, cited public research record; read its sources; work its open questions.

7 tools answering

biomedmcp

by unibio-intelligence

Integrated public biomedical research with cited, bounded evidence.

1 648 installs/wk 13 tools answering

OpenDont

by opendont

Sourced public knowledge for AI agents: search and read records with evidence; moderated writes.

9 tools answering

Atisbo Documentation

by brian8a1

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

3 tools answering

Peptides Academy

by peptidesacademy

Evidence-first peptide research: summaries and comparisons from cited dossiers, linked to courses.

4 tools answering

ImpactLine public research

by theguysaccount

Search public laws and implementation evidence with sources, scope limits and dated coverage.

3 tools answering

LiquiLens — the Failure Radar

by beepboop2025

Free bank-filing and counterparty research; cited evidence limits; public MCP needs no API key.

26 tools answering

Loreboard

by loreboard

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

4 tools answering

Lipe Court Record — questions

Answers built from our own checks of this server.

What can Lipe Court Record do?

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

Is Lipe Court Record working right now?

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

The registry lists Lipe Court Record as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

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 in the form 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 7 of them are readable on this page. This is what we observed, not what the docs claim.