mcp-registry/com.bankruptcyobserver/mcp · v1.3.0
As of 2026-10-24 03:05 UTC, the Bankruptcyobserver MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 6 minutes.
US business bankruptcy MCP: filings, dockets, documents, case summaries. Free tier + subscription.
Claude Code
claude mcp add --transport http bankruptcyobserver-mcp-server https://mcp.bankruptcyobserver.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"bankruptcyobserver-mcp-server": {
"type": "http",
"url": "https://mcp.bankruptcyobserver.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
19 of 19 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
8 parameter(s) across 7 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 13 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.bankruptcyobserver%2Fmcp/fixes
{
"name": "add_monitored_case_tool",
"description": "Add a bankruptcy case to your BankruptcyObserver.com monitoring list so BKO checks the court hourly and updates the docket every business day. Pass simple_name or a 7-digit case_number (with court when the number is reused). Subscribers only; respects your plan monitoring limit.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"court": {
"type": "string",
"description": "Court name as returned in the court field, for example \"Delaware\" or \"Texas Southern\"."
},
"case_number": {
"type": "string",
"description": "7-digit short case number alternative to simple_name."
},
"court_state": {
"type": "string",
"description": "2-letter state. Matches every district in that state."
},
"simple_name": {
"type": "string",
"description": "Case simpleName (e.g. SILVER-AIRWAYS)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "case_status",
"description": "Refresh one case from the court case summary and return the dates the court has on file (filed, last filing, converted, plan confirmed, discharged, dismissed, terminated, closed). Identifies the case by simpleName. Pass simple_name or a case number (with court when the number is reused). This calls the court, so use it for one case at a time. Single Case plan: monitored cases only. Subscribers only.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"court": {
"type": "string",
"description": "Court name as returned in the court field, for example \"Delaware\" or \"Texas Southern\"."
},
"simpleName": {
"type": "string",
"description": "Alias for simple_name."
},
"case_number": {
"type": "string",
"description": "7-digit short case number alternative to simple_name."
},
"court_state": {
"type": "string",
"description": "2-letter state. Matches every district in that state."
},
"simple_name": {
"type": "string",
"description": "Case simpleName (e.g. adaptive-phage-therapeutics)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_subscription_tool",
"description": "Check your MCP subscription status and remaining quota. Uses credentials from the request if api_key omitted.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"api_key": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.bankruptcyobserver/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.bankruptcyobserver/mcp"}) over MCP.
get_docket_entries_tool ~604 tokensget_cases_by_date_range_tool ~371 tokensget_document_cost_tool ~362 tokenssearch_bankruptcy_cases_tool ~354 tokensget_cases_by_industry_tool ~352 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.bankruptcyobserver%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.bankruptcyobserver%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.bankruptcyobserver%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.bankruptcyobserver%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.bankruptcyobserver%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:35c29e9e0fd776c0…, first seen 2026-10-22, included at leaf 48440 of 56,176. Version history · verify what your client received.
Compare: most reliable database servers · most reliable retrieval servers · most reliable other servers · most reliable data servers · most reliable files servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-24 03:05 UTC, the Bankruptcyobserver MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 10 outages in 90 days, with a median recovery of 6 minutes.
Bankruptcyobserver MCP server advertises 19 tools, including add_monitored_case_tool, case_status, check_subscription_tool, get_case_by_case_number_tool, get_case_by_ein_tool.
Point your MCP client at this streamable-http endpoint: https://mcp.bankruptcyobserver.com/mcp
Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.