# Pacer (npm · @pipeworx/mcp-pacer)

PACER Case Locator (PCL) MCP — live US federal court case & party search on the user's OWN PACER…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-pacer/pacer-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-pacer/pacer-mcp)
- npm · `@pipeworx/mcp-pacer`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-pacer/pipeworx-mcp-pacer.md), [page](https://verifymcp.io/servers/pipeworx-io-pacer/pipeworx-mcp-pacer)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-pacer`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-pacer).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 700 tokens (~350/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Pacer MCP server?

Pacer runs locally as an npm package, launched with npx -y @pipeworx/mcp-pacer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-pacer -- npx -y @pipeworx/mcp-pacer
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-pacer": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pacer"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-pacer": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pacer"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-pacer -- npx -y @pipeworx/mcp-pacer
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-pacer": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-pacer"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-pacer --command npx --arg -y --arg @pipeworx/mcp-pacer
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-pacer:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-pacer"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-pacer": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-pacer"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-pacer -t stdio -c npx -a -y @pipeworx/mcp-pacer
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-pacer": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pacer"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, +16)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `pacer_case_search` (~398 tokens)

Find US federal court cases by party name, case title, or case number — live search of the PACER Case Locator (PCL) across every federal district, bankruptcy, and appellate court. Returns case number, title, court, filing date, nature of suit, and case type. Requires your own PACER credentials (NextGen); PACER charges your account per search ($0.10/page, capped). Example: pacer_case_search({ case_title: "Lytx v. Sanderson", _apiKey: "myuser:mypass" }) or pacer_case_search({ party_name: "Nicholas Henderson", court_id: "ilndc", _apiKey: "myuser:mypass" })

Input parameters:

- `_apiKey` (string, required): Your PACER credentials as "username:password" (NextGen PACER account). PACER bills your account per search.
- `case_number` (string): Full case number, e.g. "1:2015cv01445".
- `case_title` (string): Case title / caption text, e.g. "Lytx, Inc. v. Sanderson" (not case-sensitive).
- `court_id` (string): Optional court ID to restrict the search, e.g. "ilndc" (N.D. Illinois district) or "ilnbk" (bankruptcy).
- `date_filed_from` (string): Optional filing-date lower bound, format yyyy-MM-dd.
- `date_filed_to` (string): Optional filing-date upper bound, format yyyy-MM-dd.
- `page` (integer): Optional 0-based result page (up to 54 matches per page). Default 0.
- `party_name` (string): Party name to search for, e.g. "Nicholas Henderson" or "Smith" (routed to a party search). Provide at least one of party_name, case_title, or case_number.

### `pacer_party_search` (~250 tokens)

Find parties across US federal court cases by name — live PACER Case Locator (PCL) party search across all federal courts. Returns each matching party (name, role) with the associated case number, court, and case title. Requires your own PACER credentials (NextGen); PACER charges your account per search ($0.10/page, capped). Example: pacer_party_search({ party_name: "Nicholas Henderson", _apiKey: "myuser:mypass" })

Input parameters:

- `_apiKey` (string, required): Your PACER credentials as "username:password" (NextGen PACER account). PACER bills your account per search.
- `court_id` (string): Optional court ID to restrict the search, e.g. "ilndc".
- `page` (integer): Optional 0-based result page (up to 54 matches per page). Default 0.
- `party_name` (string, required): Party name to search for, e.g. "Nicholas Henderson" or "Smith". Required.
- `role` (string): Optional party role code to filter by, e.g. "dft" (defendant) or "pla" (plaintiff).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-pacer/pipeworx-mcp-pacer#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 65
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Pacer MCP server?

Pacer is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pacer. PACER Case Locator (PCL) MCP, live US federal court case & party search on the user's OWN PACER… This page covers its npm package (@pipeworx/mcp-pacer).

### Is the Pacer MCP server safe to use?

Pacer scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Pacer MCP server expose?

Pacer exposes 2 tools: pacer_case_search, pacer_party_search. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.

### Is the Pacer MCP server still maintained?

Pacer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Pacer MCP server under?

Pacer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-pacer
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-pacer
- Repository: https://github.com/pipeworx-io/mcp-pacer
- Website: https://pipeworx.io/packs/pacer
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-pacer/pipeworx-mcp-pacer.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-pacer/pipeworx-mcp-pacer.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-pacer/pipeworx-mcp-pacer