Lipe Court Record
REMOTE · LIPE-API-PRODUCTION.UP.RAILWAY.APP
Search page-cited evidence from the public court record in Lipe v. Lupus Superior.
Available components
Last scanned (4 hours ago)
Scores higher than 8% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 22 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 10 Oct 26 0
- Schema quality: 70 → 81 ▼ functional
- 2 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- 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 security
- Schema quality: 56 → 70 ▼ functional
- New tool “list_cases” functional
- “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” cosmetic
- 8 Sept 26 0
- 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 security
- Schema quality: 44 → 56 ▼ functional
- New tool “list_record_limitations” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://lipe-api-production.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lipe-api-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lipe-api-production.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://lipe-api-production.up.railway.app/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch ~46
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | – | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_case_overview ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| authoritative_next_step | string | yes | – |
| case | object | yes | – |
| case_id | string | yes | – |
| last_reviewed_at | string | yes | – |
| limitations | array | yes | – |
| schema_version | string | yes | – |
| sections | array | yes | – |
| type | string | yes | – |
No examples provided.
grep ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case | – | – | – |
| case_sensitive | boolean | – | – |
| document | – | – | – |
| limit | integer | – | – |
| mode | string | – | – |
| pattern | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| case_sensitive | boolean | yes | – |
| documents_with_matches | integer | yes | – |
| matches | array | yes | – |
| mode | string | yes | – |
| notice | string | yes | – |
| pages_with_matches | integer | yes | – |
| pattern | string | yes | – |
| per_document | array | yes | – |
| scope | string | yes | – |
| timed_out | boolean | yes | – |
| total_matches | integer | yes | – |
| truncated | boolean | yes | – |
No examples provided.
list_case_topics ~52
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| last_reviewed_at | string | yes | – |
| limitations | array | yes | – |
| schema_version | string | yes | – |
| topics | array | yes | – |
| type | string | yes | – |
No examples provided.
list_cases ~66
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cases | array | yes | – |
| how_to_use | string | yes | – |
| schema_version | string | yes | – |
| type | string | yes | – |
No examples provided.
list_record_limitations ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | yes | – |
| how_to_use | string | yes | – |
| schema_version | string | yes | – |
| sections | array | yes | – |
| type | string | yes | – |
No examples provided.
search ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
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.
remote · lipe-api-production.up.railway.app
claude mcp add --transport http dalenz50010-lipe-court-record 'https://lipe-api-production.up.railway.app/mcp'
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 23 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 7 tools: list_cases, search, fetch, grep, get_case_overview, and 2 more. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Does the Lipe Court Record MCP server require authentication?
Its publisher declares no required credentials for Lipe Court Record. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Lipe Court Record MCP server still maintained?
Lipe Court Record is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.