Tx Medical Exclusions MCP server

@pipeworx/tx-medical-exclusions

Texas HHSC Office of Inspector General (OIG) Medicaid Provider Exclusions Database screening — check a provider by name, NPI or license number against the ~13,400-row list of providers ever excluded from Texas's Medicaid program, the state-level counterpart to the federal HHS OIG LEIE (leie pack) and the sibling of ny-omig-exclusions (New York) and ca-medical-exclusions (California).

Part of Pipeworx — an MCP gateway connecting AI agents to 1745+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

provider against the HHSC OIG Exclusions Database. An NPI or license match is an identification (both are exact, provider-specific identifiers); a name match — even an exact one — is a candidate lead only, since the list carries no date of birth and most individual rows have no company name to disambiguate same-named providers. Every match carries HHSC OIG's own free-text reason and a currently_excluded flag derived from whether the provider has since been reinstated.

• txmedicalcheck_exclusion(name?, npi?, license?, limit?) — screens a

many are currently excluded vs. reinstated, how many carry an NPI or license number, occupation diversity, and the oldest/newest exclusion date.

• txmedicalexclusion_coverage() — total exclusions ever recorded, how

Auth

Keyless.

Data sources

HHSC OIG "Download Exclusions File" page. The downloadable file itself (CompanyName, LastName, FirstName, MidInitial, Occupation, LicenseNumber, NPI, StartDate, AddDate, ReinstatedDate, EligibleToReapplyDate, Waiver, WebComments) is fetched via an ASP.NET VIEWSTATE postback from this same URL — see "Why a VIEWSTATE postback" below.

• — the

Excluded Individuals/Entities Search" (currently-excluded only; this pack's dataasof/source_url always points at the download file, not this page).

• — the online "List of

Why no open-data-portal mirror — checked, not assumed

California's S&I list has a stable CKAN resourceid mirror on the CHHS Open Data Portal. Texas does not** have an equivalent for this dataset: a Socrata catalog search of data.texas.gov (api.us.socrata.com/api/catalog/v1?domains=data.texas.gov) for "OIG exclusion", "HHSC exclusion", "excluded provider", "inspector general" and "Medicaid exclusion" (2026-10-08) returned zero matching datasets. The HHSC OIG portal is the only source.

Why a VIEWSTATE postback, not a direct URL

The visible "Download TEXT version of the Exclusions Database File" link on the HHSC OIG page is javascript:doPostBack(...), not a plain href — a classic ASP.NET WebForms (DotNetNuke) postback, the same shape as referenceaspnetpostbackdownloads.md / the louisiana-code precedent (a VIEWSTATE form is not a wall). scripts/bake-index.mjs replays the flow: GET the page, extract VIEWSTATE/VIEWSTATEGENERATOR/EVENTVALIDATION from the hidden inputs plus the session cookies, then POST those fields back with EVENTTARGET set to the download LinkButton's control ID. The response is the file itself (Content-Disposition: attachment;filename=TexasExclusionsData.txt) — the filename embeds the request date, confirming HHSC generates this export live from its database on every request, which is why this pack uses the capture timestamp itself as dataas_of rather than scraping a separate "last updated" banner (the page's own literaldatelastupd placeholder span is empty on a fresh GET).

Why this is baked, not a live proxy

Shortened. The full README is on GitHub.