# Harris County (npm · @pipeworx/mcp-harris-county)

Harris County (TX) District Clerk civil dockets — every civil case filed in Texas's largest…

- Trust score: 83/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`: 87/100, [markdown](https://verifymcp.io/servers/pipeworx-io-harris-county/harris-county-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-harris-county/harris-county-mcp)
- npm · `@pipeworx/mcp-harris-county`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-harris-county/pipeworx-mcp-harris-county.md), [page](https://verifymcp.io/servers/pipeworx-io-harris-county/pipeworx-mcp-harris-county)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-harris-county`
- 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-harris-county).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 833 tokens (~208/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Harris County MCP server?

Harris County runs locally as an npm package, launched with npx -y @pipeworx/mcp-harris-county. 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-harris-county -- npx -y @pipeworx/mcp-harris-county
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-04 (score 83, +1)

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

### 2026-11-03 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 67, −14)

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

### 2026-10-31 (score 81, +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-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `harris_civil_search_party` (~387 tokens)

Find Harris County (Houston, TX) state civil court cases involving a named party — the "is this company being sued, and by whom" question that federal docket sources (court-listener, PACER) structurally cannot answer, because Texas state district court filings are not in them. Matches the party name as a substring against plaintiff, defendant and the clerk's case style, so "KROGER" finds "KROGER TEXAS L.P." and "THE KROGER CO". Optionally restrict to the side the party is on (role=defendant|plaintiff), case_type, or a filed-date range. Returns each case with cause number, court, case type, decoded status, filing and judgment dates, both parties and both attorneys with their Texas State Bar numbers. NOTE the corpus is a rolling activity window: an empty result means no matching case in the ingested window, not that the party has never been sued.

Input parameters:

- `case_type` (string): Substring of the clerk's case type, e.g. "Motor Vehicle", "Debt", "Contract", "Injury".
- `filed_after` (string): Only cases filed on or after this date (YYYY-MM-DD).
- `filed_before` (string): Only cases filed on or before this date (YYYY-MM-DD).
- `limit` (number|string): Max cases (1-100, default 25).
- `name` (string, required): Party name to search for, e.g. "AMAZON LOGISTICS", "KROGER", "HALLIBURTON". Matched as a case-insensitive substring; multiple words are AND-ed so order does not matter.
- `role` (string): Restrict to one side: "defendant" (being sued) or "plaintiff" (suing). Default searches both plus the case style.

### `harris_civil_case` (~139 tokens)

Full detail for one Harris County (TX) civil case by its cause number (e.g. "202662585"): case type, status, filing and judgment dates, the style, both sides' attorneys with State Bar numbers, and every party on the case — plaintiffs, defendants, intervenors, registered agents — which the case index alone does not carry. Party locations are city and state. Use after harris_civil_search_party returns a case_number.

Input parameters:

- `case_number` (string, required): The cause number as published by the District Clerk, e.g. "202662585". A few carry a trailing letter for severed matters.

### `harris_civil_recent_filings` (~169 tokens)

Recently filed Harris County (Houston, TX) civil cases, newest first — the "what is being filed in Houston right now" view. Optionally filter by case_type (e.g. "Motor Vehicle", "Debt", "Contract") or court number. Returns cause number, court, case type, decoded status, filing date, both parties and both attorneys.

Input parameters:

- `case_type` (string): Substring of the clerk's case type, e.g. "Motor Vehicle", "Debt".
- `court` (string): District court number as published, e.g. "0055".
- `filed_after` (string): Only cases filed on or after this date (YYYY-MM-DD).
- `limit` (number|string): Max cases (1-100, default 25).

### `harris_civil_coverage` (~82 tokens)

What this Harris County docket corpus actually covers — case and party row counts, the filing-date range present, and the clerk files it was last built from. Call this before concluding anything from an empty search result: the corpus is a rolling activity window, and this tool is how you tell "no such case" from "not in the window covered".

## Diagnostics

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

## Score history

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

## Common questions

### What is the Harris County MCP server?

Harris County is an MCP server listed in the public MCP registry as io.github.pipeworx-io/harris-county. Harris County (TX) District Clerk civil dockets, every civil case filed in Texas's largest… This page covers its npm package (@pipeworx/mcp-harris-county).

### Is the Harris County MCP server safe to use?

Harris County 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 Harris County MCP server expose?

Harris County exposes 4 tools: harris_civil_search_party, harris_civil_case, harris_civil_recent_filings, harris_civil_coverage. Their descriptions and schemas cost roughly 777 tokens of context every time the server is loaded.

### Is the Harris County MCP server still maintained?

Harris County 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 Harris County MCP server under?

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

### What did VerifyMCP test on the Harris County MCP server?

VerifyMCP ran 15 checks on Harris County, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Harris County: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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