MCP.Market

Recap MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/recap·v0.2.0

RECAP — the actual documents filed in US federal court cases.

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

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Recap yet.

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

Recap 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 Recap compares

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

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
60 ms
faster than 91% of 30,031 servers

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

Install Recap in Claude Code, Cursor or VS Code

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

What the publisher says

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

RECAP — documents filed in US federal court cases

Direct links to the complaints, motions, orders and exhibits filed in federal cases. No API key, no PACER fee.

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

Auth

None.

How this is possible without a key

RECAP documents are not in CourtListener's bulk export. They are mirrored to the Internet Archive under an identifier that can be derived:

gov.uscourts.<court_id>.<pacer_case_id>

Federal docket coverage carries courtid for 100% of dockets and pacercase_id for 84.8%, so a case's filings have a computable address. No agreement with anyone, no per-page charge.

What you get, and what you don't

You get: a link to each PDF, its docket-entry number and attachment number, its size, and the docket sheet where one exists.

You don't get text. Measured across 400 dockets: 141 archive items carry PDFs and none carry extracted text. Reading a filing means opening the document. Making these searchable would be an OCR project; this is not one.

Coverage is partial, and uneven

RECAP holds what PACER users have paid for and contributed, so coverage follows where lawyers use it. Measured over 400 dockets across 16 courts:

Overall: 35.8%.

The consequence matters more than the number: "no documents" means none have been contributed to RECAP — not that nothing was filed. Roughly two cases in three will come back empty, and every response says so. Treating an empty result as a fact about the court record would be wrong most of the time.

Tool

recapfilings — give it a docketid from any docket search, or a court plus docket_number.

recap_filings({docket_id: 73433096})
  → V.O.S. Selections, Inc. v. Trump (cafc), 18 documents

Filenames encode the structure: ….12.0.pdf is docket entry 12, ….12.1.pdf its first attachment. That ordering is the only structure the archive provides — there are no document titles — so it is returned rather than hidden.

Related

bankruptcy_search — find the docket first

  • federalcivilsearch, federalcriminalsearch, federalappealsearch,
  • court-listener — opinions and full case text, a different corpus entirely

Data sources

  • https://archive.org/ — RECAP archive items
  • Federal docket coverage (CourtListener bulk data, Public Domain Mark)

RECAP exists because Free Law Project built it and PACER users contributed to it:

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/recap/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.

Shortened. The full README is on GitHub.

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

Recap: common questions

Is Recap MCP server safe?
Mostly: it is graded B (77/100). Read the Recap safety report
How do I install Recap?
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 Recap need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Recap maintained?
The last commit was 39 days ago (2026-09-26). The latest release is v0.2.0.
Is Recap up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Recap compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 60 ms (faster than 91% of 30,031 servers). Full comparison.

More from pipeworx-io →