Harris County
NPM · @PIPEWORX/MCP-HARRIS-COUNTY · 2 COMPONENTS
Harris County (TX) District Clerk civil dockets — every civil case filed in Texas's largest…
Available components
Last scanned (19 hours ago)
Scores higher than 76% of npm servers
Category Documents and Files
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-harris-county). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-harris-county@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-harris-county |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-harris-county/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637388111 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3bfa593898416e3998951a9afe7a5feec905467b65e34ac60cc1eec62c3d2849655ae6976f4953a90409269ffecf038ad75652951aa3ac14947e59d4f |
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 →
harris_civil_case ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_number | string | yes | The cause number as published by the District Clerk, e.g. "202662585". A few carry a trailing letter for severed matters. |
No output schema declared.
No examples provided.
harris_civil_coverage ~82
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".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
harris_civil_recent_filings ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
harris_civil_search_party ~387
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-harris-county
claude mcp add pipeworx-io-harris-county -- npx -y @pipeworx/mcp-harris-county
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.