Skip to content
Back to the index

pacer

pipeworx.ioInfrastructure

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

Pacer is a Pipeworx MCP server that exposes tools for searching US federal court cases and parties through the PACER Case Locator. It supports searches by party name, case title, case number, and court, while using the user's PACER credentials and account billing.

Inferred · not functionally tested

WebAPICloud-managed
pacer preview
Visit pipeworx.io

Overview

5 features

Purpose: Finding federal court cases and parties across PACER without manually searching each court system.

Inferred · not functionally tested

Audience: legal researchers, attorneys, and developers building legal research workflows

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

pacer sits in PulseGate's API design, testing & docs category. Inferred · not functionally tested: It focuses on finding federal court cases and parties across PACER without manually searching each court system. Inferred · not functionally tested: pacer is a B2B product aimed at legal researchers, attorneys, and developers building legal research workflows. Basis unknown · not verified: It ships for the web and API.

It is developed by Pipeworx. Inferred · not functionally tested: Among its 5 catalogued features are case search, party search, and court filtering. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Case search
  • Party search
  • Court filtering
  • Case metadata
  • MCP tools

Topics: Inferred · not functionally tested

Tags
pacer-searchfederal-court-recordslegal-researchmcp-server

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCP
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 00:02 UTC
    Pacer seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about pacer

What does pacer do?
Inferred · not functionally tested: Pacer focuses on finding federal court cases and parties across PACER without manually searching each court system. It is catalogued under API design, testing & docs on PulseGate.
Who is pacer for?
Inferred · not functionally tested: pacer is a B2B product built for legal researchers, attorneys, and developers building legal research workflows.
What platforms does pacer run on?
Basis unknown · not verified: pacer runs on the web and API.
Is pacer still maintained?
Unverified. pacer has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
Who develops pacer?
pacer is developed by Pipeworx.
Does pacer have an API or integrations?
Inferred · not functionally tested: Yes — pacer exposes an MCP server.

Similar projects

Closest matches by what these projects do