# Docket Alarm (npm · @pipeworx/mcp-docket-alarm)

Docket Alarm MCP — state + county + federal court dockets (docketalarm.com)

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

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-docket-alarm/docket-alarm-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-docket-alarm/docket-alarm-mcp)
- npm · `@pipeworx/mcp-docket-alarm`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-docket-alarm/pipeworx-mcp-docket-alarm.md), [page](https://verifymcp.io/servers/pipeworx-io-docket-alarm/pipeworx-mcp-docket-alarm)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-docket-alarm`
- 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-docket-alarm).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 573 tokens (~191/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Docket Alarm MCP server?

Docket Alarm runs locally as an npm package, launched with npx -y @pipeworx/mcp-docket-alarm. 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-docket-alarm -- npx -y @pipeworx/mcp-docket-alarm
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +1)

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

### 2026-11-03 (score 82, +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-11-01 (score 81, +2)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `docketalarm_search` (~186 tokens)

Search court dockets (state + federal) for `<query>` — full-text search across 675M+ US state, county, and federal court dockets (deeper state coverage than CourtListener). Returns matching cases with court, docket number, title, filing date, and link. Example: docketalarm_search({ q: "patent infringement Apple", limit: 20, _apiKey: "user@example.com:yourpassword" })

Input parameters:

- `_apiKey` (string, required): Docket Alarm credentials as "username:password" from your docketalarm.com account.
- `limit` (integer): Max results to return (default 20, max 50).
- `offset` (integer): Starting offset into the result set (for pagination).
- `q` (string, required): Full-text search query. Supports fielded search, e.g. is:docket "Acme Corp".

### `docketalarm_get_docket` (~174 tokens)

Get full docket detail for a case — returns case title, parties, filing date, and docket entries for a specific court + docket number. Cached documents are free. Example: docketalarm_get_docket({ court: "U.S. District Court, N.D. California", docket: "5:11-cv-01846", _apiKey: "user@example.com:yourpassword" })

Input parameters:

- `_apiKey` (string, required): Docket Alarm credentials as "username:password" from your docketalarm.com account.
- `court` (string, required): Full court name, exactly as returned by docketalarm_search (e.g. "U.S. District Court, N.D. California").
- `docket` (string, required): Docket / case number (e.g. "5:11-cv-01846").

### `docketalarm_search_pacer` (~158 tokens)

Search federal PACER dockets by party — live party-name search across federal PACER (Appellate, Bankruptcy, Civil, Criminal, MDL). Note: this passes live PACER search fees at cost. Returns matching federal cases with court, docket, title, and filing date. Example: docketalarm_search_pacer({ party_name: "Microsoft Corporation", _apiKey: "user@example.com:yourpassword" })

Input parameters:

- `_apiKey` (string, required): Docket Alarm credentials as "username:password" from your docketalarm.com account.
- `court_region` (string): Optional regional filter to narrow the PACER search.
- `party_name` (string, required): Company or individual party name to search for on PACER.

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Docket Alarm MCP server?

Docket Alarm is an MCP server listed in the public MCP registry as io.github.pipeworx-io/docket-alarm. Docket Alarm MCP, state + county + federal court dockets (docketalarm.com). This page covers its npm package (@pipeworx/mcp-docket-alarm).

### Is the Docket Alarm MCP server safe to use?

Docket Alarm scores 83 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 Docket Alarm MCP server expose?

Docket Alarm exposes 3 tools: docketalarm_search, docketalarm_get_docket, docketalarm_search_pacer. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

### Is the Docket Alarm MCP server still maintained?

Docket Alarm 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 Docket Alarm MCP server under?

Docket Alarm 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-docket-alarm
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-docket-alarm
- Repository: https://github.com/pipeworx-io/mcp-docket-alarm
- Website: https://pipeworx.io/packs/docket-alarm
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-docket-alarm/pipeworx-mcp-docket-alarm.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-docket-alarm/pipeworx-mcp-docket-alarm.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-docket-alarm/pipeworx-mcp-docket-alarm