# Tx Medical Exclusions (npm · @pipeworx/mcp-tx-medical-exclusions)

Texas HHSC Office of Inspector General (OIG) Medicaid Provider Exclusions Database screening…

- Trust score: 78/100 (medium)
- Change this week: 0
- 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-tx-medical-exclusions/tx-medical-exclusions-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-tx-medical-exclusions/tx-medical-exclusions-mcp)
- npm · `@pipeworx/mcp-tx-medical-exclusions`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-tx-medical-exclusions/pipeworx-mcp-tx-medical-exclusions.md), [page](https://verifymcp.io/servers/pipeworx-io-tx-medical-exclusions/pipeworx-mcp-tx-medical-exclusions)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-tx-medical-exclusions`
- Version: `0.2.0`
- 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-tx-medical-exclusions).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 699 tokens (~349/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Tx Medical Exclusions MCP server?

Tx Medical Exclusions runs locally as an npm package, launched with npx -y @pipeworx/mcp-tx-medical-exclusions. 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-tx-medical-exclusions -- npx -y @pipeworx/mcp-tx-medical-exclusions
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-tx-medical-exclusions -- npx -y @pipeworx/mcp-tx-medical-exclusions
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-tx-medical-exclusions --command npx --arg -y --arg @pipeworx/mcp-tx-medical-exclusions
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

- [functional regression] Security disclosure: fail → unverified

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `tx_medical_check_exclusion` (~407 tokens)

Is this healthcare provider excluded from the Texas Medicaid program? Screens a person or business name, an NPI, and/or a license number against the Texas HHSC Office of Inspector General (OIG) Medicaid Provider Exclusions Database — the state-level counterpart to the federal HHS OIG LEIE (see the leie pack) for Texas specifically, and the sibling of ny_omig_check_exclusion (New York) and ca_medical_check_exclusion (California). Answers "is this provider excluded from Texas Medicaid", "check this NPI against the Texas exclusions list", or pre-payment/credentialing screening for a Texas Medicaid provider. An NPI or license-number match is an IDENTIFICATION (both are exact, provider-specific identifiers); a name match — even an exact one — is a CANDIDATE lead only, since this list carries no date of birth to tell same-named providers apart. Every match carries HHSC OIG's own free-text reason (e.g. "Federal mandated exclusion", "Conviction relating to Healthcare Fraud") and a currently_excluded flag DERIVED from whether the provider has since been reinstated — this dataset covers everyone EVER excluded, not only those currently excluded. Pass npi or license to turn a name lead into an identification. Sourced from the Texas HHSC OIG Exclusions Database File, keyless.

Input parameters:

- `license` (string): Texas professional license number, if known. A license match is an identification.
- `limit` (number): Maximum matches to return (default 10, max 50).
- `name` (string): Provider or business name to screen, e.g. "John Smith" or "Acme Pharmacy Corp". Matched against the provider's individual name and company name, any word order.
- `npi` (string): The provider's 10-digit NPI, if known. An NPI match is an identification rather than a name lead — always pass it when known.

### `tx_medical_exclusion_coverage` (~233 tokens)

What the Texas HHSC OIG Medicaid Provider Exclusions data covers and how current it is: total exclusions ever recorded, how many are currently excluded vs. reinstated, how many carry an NPI or license number, how many distinct occupations appear, the oldest and newest exclusion dates, and when this pack's copy was captured. Use to check the screening data is fresh enough to rely on before a compliance decision, and to see the one-line notes on the free-text reason field and the ever-vs-currently-excluded distinction. Pass year (e.g. 2025) or start_date/end_date to instead COUNT how many exclusions have an effective date in that year or range, counted over the whole 13,000+ row list, not a page — answers "how many Texas HHSC OIG exclusions took effect in 2025". The response names the date field counted (excluded_since / HHSC's StartDate — never added_date, which answers a different question and gives a different number). Sourced from the Texas HHSC OIG Exclusions Database File, keyless.

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Tx Medical Exclusions MCP server?

Tx Medical Exclusions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tx-medical-exclusions. Texas HHSC Office of Inspector General (OIG) Medicaid Provider Exclusions Database screening… This page covers its npm package (@pipeworx/mcp-tx-medical-exclusions).

### Is the Tx Medical Exclusions MCP server safe to use?

Tx Medical Exclusions scores 78 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 Tx Medical Exclusions MCP server expose?

Tx Medical Exclusions exposes 2 tools: tx_medical_check_exclusion, tx_medical_exclusion_coverage. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.

### Is the Tx Medical Exclusions MCP server still maintained?

Tx Medical Exclusions 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 Tx Medical Exclusions MCP server under?

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