Pacer
NPM · @PIPEWORX/MCP-PACER · 2 COMPONENTS
PACER Case Locator (PCL) MCP — live US federal court case & party search on the user's OWN PACER…
Available components
Last scanned (6 hours ago)
Scores higher than 68% of npm servers
Category Search and Retrieval
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-pacer). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-pacer@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-pacer |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-pacer/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685239109 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bd03daf3a36aebf0674f8247f25599ac5130ba0fc967a159835349a4efabc38df534a9eb3a38e1fd6707df1fa976be6d46d68580b8a632497b98755ad |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pacer_case_search ~398
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | 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. |
No output schema declared.
No examples provided.
pacer_party_search ~250
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | 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 | yes | 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). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-pacer
claude mcp add pipeworx-io-pacer -- npx -y @pipeworx/mcp-pacer
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.