# Lipe Court Record (remote · lipe-api-production.up.railway.app)

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

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `lipe-api-production.up.railway.app`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dalenz50010-lipe-court-record/lipe-api-production.md), [page](https://verifymcp.io/servers/dalenz50010-lipe-court-record/lipe-api-production)

## Channel facts

- Endpoint: `https://lipe-api-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 635 tokens (~70/item across 9 items; 6 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Lipe Court Record MCP server?

Lipe Court Record is a hosted endpoint at https://lipe-api-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dalenz50010-lipe-court-record": {
      "type": "remote",
      "url": "https://lipe-api-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dalenz50010-lipe-court-record --url 'https://lipe-api-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dalenz50010-lipe-court-record:
    url: "https://lipe-api-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dalenz50010-lipe-court-record": {
      "Transport": "http",
      "Url": "https://lipe-api-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dalenz50010-lipe-court-record -t streamable-http -u 'https://lipe-api-production.up.railway.app/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_case_overview” rewrote its description, which is the text the model reads
- [security] Tool “list_case_topics” rewrote its description, which is the text the model reads
- [security] Tool “list_record_limitations” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 56 → 70
- [functional] New tool “list_cases”
- [cosmetic] “get_case_overview” added an optional parameter “case”
- [cosmetic] “list_case_topics” added an optional parameter “case”
- [cosmetic] “list_record_limitations” added an optional parameter “case”
- [cosmetic] “search” added an optional parameter “case”

### 2026-09-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 73, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 44 → 56
- [functional] New tool “list_record_limitations”

## MCP tools (6)

### `list_cases` (~66 tokens)

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.

Output parameters:

- `cases` (array)
- `how_to_use` (string)
- `schema_version` (string)
- `type` (string)

### `search` (~114 tokens)

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.

Input parameters:

- `case`
- `query` (string, required)

Output parameters:

- `results` (array)

### `fetch` (~46 tokens)

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.

Input parameters:

- `id` (string, required)

Output parameters:

- `id` (string)
- `metadata`
- `text` (string)
- `title` (string)
- `url` (string)

### `get_case_overview` (~57 tokens)

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.

Input parameters:

- `case`

Output parameters:

- `authoritative_next_step` (string)
- `case` (object)
- `case_id` (string)
- `last_reviewed_at` (string)
- `limitations` (array)
- `schema_version` (string)
- `sections` (array)
- `type` (string)

### `list_case_topics` (~52 tokens)

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.

Input parameters:

- `case`

Output parameters:

- `case_id` (string)
- `last_reviewed_at` (string)
- `limitations` (array)
- `schema_version` (string)
- `topics` (array)
- `type` (string)

### `list_record_limitations` (~83 tokens)

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.

Input parameters:

- `case`

Output parameters:

- `case_id` (string)
- `how_to_use` (string)
- `schema_version` (string)
- `sections` (array)
- `type` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dalenz50010-lipe-court-record/lipe-api-production#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 70
- 2026-09-02: 70

## Common questions

### What is the Lipe Court Record MCP server?

Lipe Court Record is an MCP server listed in the public MCP registry as io.github.dalenz50010/lipe-court-record. Search page-cited evidence from the public court record in Lipe v. Lupus Superior. This page covers its hosted endpoint (https://lipe-api-production.up.railway.app/mcp).

### Is the Lipe Court Record MCP server safe to use?

Lipe Court Record scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Lipe Court Record MCP server expose?

Lipe Court Record exposes 6 tools: list_cases, search, fetch, get_case_overview, list_case_topics, list_record_limitations. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.

### Does the Lipe Court Record MCP server require authentication?

No. We connected to Lipe Court Record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Lipe Court Record MCP server still maintained?

Lipe Court Record is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://lipe-api-production.up.railway.app/mcp
- Website: https://lipe-api-production.up.railway.app/connect
- Changelog RSS feed: https://verifymcp.io/servers/dalenz50010-lipe-court-record/lipe-api-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/dalenz50010-lipe-court-record/lipe-api-production.json
- HTML version of this page: https://verifymcp.io/servers/dalenz50010-lipe-court-record/lipe-api-production