Lipe Court Record MCP server
io.github.dalenz50010/lipe-court-recorddalenz50010streamable-httpv0.3.0Scanned
Search page-cited evidence from the public court record in Lipe v. Lupus Superior.
7 tools: 7 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Lipe Court Record MCP server can do
The Lipe Court Record MCP server is published by the GitHub account dalenz50010. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (list_record_limitations); 2 tools bring in text other people can write (fetch and list_record_limitations).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 21, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Only reads 7Show 7 read-only tools
fetchFetch one search result's exact physical PDF page, reviewed evidence, provenance, and permanent citation URL.Reads text others writeNo findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
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…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_record_limitations" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "document": it reads documents.
- untrusted-inputThe description's first sentence says "list" and "review": it reads comments, which other people can write.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 404.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude 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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lipe-court-record. Review it before you use it.
Capability tags behind 2 rules
- mcp__lipe-court-record__fetch untrusted-input
- mcp__lipe-court-record__list_record_limitations private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.dalenz50010/lipe-court-record/verify?hash=72a82f8775d8bde05d1ea9d60a6f359931139bcd8a18c500983fc7bf79ae3860" | jq -e '.changed == false'Pinned hash 72a82f8775d8, from Oct 21, 2026, 19:09 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.dalenz50010/lipe-court-record/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.dalenz50010/lipe-court-record)Source: MCP Registry. Synced Oct 21, 2026, 18:29 UTC.
Lipe Court Record MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Lipe Court Record MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Lipe Court Record MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Lipe Court Record MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Lipe Court Record MCP server have?
- 7 tools: 7 read. list_cases, search, fetch, grep, get_case_overview, list_case_topics and list_record_limitations.
Does the Lipe Court Record MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Lipe Court Record MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Lipe Court Record MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.