Ny Omig Exclusions

What Ny Omig Exclusions MCP server does

Ny Omig Exclusions MCP server screens providers against New York State OMIG's Medicaid exclusion list. Queries can use a provider name, NPI, or license number, with an optional result limit. The source data contains roughly 9,100 exclusion records and includes provider names, license numbers, NPIs, provider types, and exclusion effective dates.

An NPI or license match identifies a specific provider because those identifiers are provider-specific. A name match is only a candidate lead, including when the spelling appears to match exactly. OMIG's published list does not include a date of birth or address, so the result cannot distinguish between providers who share a name.

How it works

Ny Omig Exclusions MCP server uses OMIG's tab-delimited export rather than a JSON or REST API. The repository's bake script converts the published table into generated TypeScript data, which is deployed as a baked index. Calls receive that index at runtime; a missing or malformed index produces an error instead of a false “not found” response.

The copy is not automatically live. Re-run the repository's bake script and redeploy to refresh it. Each response includes data_as_of, which indicates how the served copy compares with OMIG's own last-updated date. The server also reads OMIG's smaller “last 30 days” page to obtain that update-date banner. Responses include online_search_url, linking to OMIG's own search page for direct checking.

Setup and configuration

The service is keyless and needs no authentication. For a remote MCP connection, configure an MCP client with:

{
  "mcpServers": {
    "ny-omig-exclusions": {
      "url": "https://gateway.pipeworx.io/ny-omig-exclusions/mcp"
    }
  }
}

A local stdio installation is also available through npm:

{
  "mcpServers": {
    "ny-omig-exclusions": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-ny-omig-exclusions"]
    }
  }
}

The standalone process exposes only this pack's tools. The gateway endpoint adds shared Pipeworx meta-tools, including routing and discovery tools, so its tool list is broader than the two pack-specific tools. HTTP callers can invoke tools through the gateway's /v1/tools/ endpoint without an MCP client.

Tools and capabilities

Ny Omig Exclusions MCP server provides these pack-specific tools:

• ny_omig_check_exclusion(name?, npi?, license?, limit?) searches the baked exclusion index.
• ny_omig_exclusion_coverage() reports the number of exclusions, identifier coverage, provider-type diversity, oldest and newest exclusion dates, and OMIG's data update date.

The gateway can also accept natural-language requests through ask_pipeworx, while direct MCP calls can use the named tools and their structured arguments.

Limitations and notes

OMIG's exports do not publish exclusion reasons, statutory authority, or case citations. They contain only the provider fields and effective date listed above. Record-level details that might exist behind OMIG's web interface were not included because that interface relies on an ASP.NET session and postback flow rather than a stable query endpoint.

Name-only results must therefore be reviewed as possible matches, not treated as confirmed exclusions. For confirmation, use the supplied OMIG online-search link. The served dataset can become stale until the bake script is run again and the updated index is deployed. This is an independent, unofficial integration and is not affiliated with OMIG.