MCP.Market

Bankruptcy MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/bankruptcy·v0.2.1

Business bankruptcy filings — US federal bankruptcy courts.

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Bankruptcy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Bankruptcy tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Bankruptcy compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
140 ms
faster than 75% of 30,031 servers

Release history: 6 versions in the registry since 2026-09-16, latest 2026-10-30, typically one every 8 days.

Install Bankruptcy in Claude Code, Cursor or VS Code

claude mcp add --transport http bankruptcy https://gateway.pipeworx.io/bankruptcy/mcp
Add to Cursor

What the publisher says

From the Bankruptcy repository's README, as published. We do not edit it. Read it on GitHub

Bankruptcy — US business bankruptcy filings

Business bankruptcy filings from US federal bankruptcy courts: 1.55 million filings, searchable by company name, court and date. No API key.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Auth

None.

What this is, and what it is not

This is docket metadata: that a case exists, who filed, in which court, when it was filed, when it terminated, and which judge was assigned. It contains no filings — no petitions, schedules, motions or orders. Those live in RECAP, a separate corpus that is not keyless.

An agent that has this data knows a company filed. It does not know what the company said.

Consumer bankruptcy is deliberately excluded

Of CourtListener's 71,677,647 dockets, 35,312,051 are individual bankruptcy filings — half the corpus. They carry no business signal and are PII-adjacent, so they are excluded.

The docket export has no chapter column, so business and consumer are separated by a legal-entity-suffix test on the debtor name (Inc, LLC, Corp, Holdings, Construction, and so on), applied only inside bankruptcy courts. Two consequences worth knowing before relying on a negative result:

has never filed".

  • A sole proprietorship filing under a personal name will not appear here.
  • "No filings found" means "no business filing matched", never "this entity

Tools

Court ids follow CourtListener's convention: nysb (S.D.N.Y. Bankruptcy), deb (Delaware), txsb (S.D. Tex.), cacb (C.D. Cal.), ilnb (N.D. Ill.).

Caveats

after it is not here.

  • Quarterly snapshot. Every response carries snapshot_date. Anything filed

not recorded, never still open. Responses say this on every row.

  • dateterminated is 78.3% filled**, so a missing termination date means

filter by case type.

  • natureofsuit is sparse (14.8% corpus-wide) and cannot be relied on to

inconsistent entity suffixes. Search matches substrings for that reason.

  • Case names are as the court recorded them, including abbreviations and

Attribution

Data is CourtListener / Free Law Project, published under the Public Domain Mark. Free Law Project funds and maintains the corpus. If this pack is useful to you, is where that goes.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "bankruptcy": {
      "url": "https://gateway.pipeworx.io/bankruptcy/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/bankruptcy/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Bankruptcy: common questions

Is Bankruptcy MCP server safe?
Mostly: it is graded B (73/100). Read the Bankruptcy safety report
How do I install Bankruptcy?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Bankruptcy need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Bankruptcy maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v0.2.1.
Is Bankruptcy up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Bankruptcy compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 140 ms (faster than 75% of 30,031 servers). Full comparison.

More from pipeworx-io →