In-depth architectural comparison of the ElevenFlo MCP and CourtAPI — Federal Court Data MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
ElevenFlo MCP
Legal · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: OAuth 2.0
CourtAPI — Federal Court Data
Legal · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose ElevenFlo MCP if you need specialized Legal tools running via a hosted cloud SSE transport. Choose CourtAPI — Federal Court Data if your workspace requires Legal integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
E
Choose ElevenFlo MCP when:
You need dedicated capabilities in the Legal domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
Primary tools included: Case discovery by debtor, counsel, judge, jurisdiction, or industry, Docket browsing: first-day motions, DIP filings, plans, confirmation orders, Filing analysis extracting financing terms, covenants, recoveries with citations.
ElevenFlo MCP is categorized under Legal and uses a remote streaming HTTP/SSE transport. In contrast, CourtAPI — Federal Court Data belongs to Legal using local stdio subprocess. Select ElevenFlo MCP when you need capabilities focused on legal and CourtAPI — Federal Court Data when you require tools for legal.
Discover cases you don't have a court code or full case number for. Pass a party/company name, partial case number, or free-text keywords. The tool automatically picks the best search endpoint:
get_case
Get all metadata for a known case: title, chapter, judge, key dates (filed/closed/discharged), assets, liabilities, and the `menu` object. The `menu` has one entry per sub-resource (dockets, claims, parties, etc.) with a `modified` timestamp — `null` means that resource has never been purchased fro…
get_dockets
Get the docket sheet — all filings in chronological order with dates, descriptions, and attached document info. Supports keyword search and date/number range filtering.
get_document
Get a PDF attached to a docket entry. Checks the cache first:
get_claims
Get the bankruptcy claims register — all proofs of claim filed by creditors, with amounts (filed/allowed/paid), claim type, creditor names, and filing dates. Essential for Chapter 11 creditor analysis.
get_parties
Get all parties in a case (debtors, creditors, plaintiffs, defendants, trustees) and optionally their attorneys with firm name, contact info, and bar number. Attorney records return `null` (not an error) when they haven't been purchased for this case — use `include_attorneys=false` to suppress the…
get_creditors
Get scheduled creditors from bankruptcy Schedules D/E/F. This is different from `get_claims` — creditors listed here may not have filed a proof of claim. Use both to get a complete creditor picture.
ncl_search
Search PACER's National Case Locator across all federal courts at once. More comprehensive than `find_cases` for party name searches because it queries PACER directly. Costs PACER credits.
list_courts
List all ~200 PACER courts with their court codes and names. Filter by type: `bankruptcy`, `district`, or `appellate`.
get_pacer_credentials
Manage PACER credentials stored in CourtAPI. PACER credentials are required before any `include_live_pacer=true` call.