MCP servers observed by Lowdown
io.github.dalenz50010/lipe-court-record MCP server: daily status and tool changes
No successful response on the last 7 consecutive daily checks (2026-10-22 to 2026-10-28). Checked from one network location. 7 of 23 observed days in the last 30 had this result. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-06; no tool definition change in 15 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.dalenz50010/lipe-court-record
Does it respond?
Latest daily check: 2026-10-28: the server did not respond.
- Observed days in the last 30: 23
- Answered initialize and tools/list: 16
- Required authentication: 0
- No response: 7
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 23 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 15 compared days.
What tools does it list?
7 tools on 2026-10-21:
fetchget_case_overviewgreplist_case_topicslist_caseslist_record_limitationssearch
MCP Registry declaration
- Registry name:
io.github.dalenz50010/lipe-court-record - Declared version: 0.3.0
- Status: active
- Declared hosts:
lipe-api-production.up.railway.app