# Ny Omig Exclusions (npm · @pipeworx/mcp-ny-omig-exclusions)

New York State OMIG Medicaid provider exclusion screening — fleet #2788.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-ny-omig-exclusions/ny-omig-exclusions-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ny-omig-exclusions/ny-omig-exclusions-mcp)
- npm · `@pipeworx/mcp-ny-omig-exclusions`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ny-omig-exclusions/pipeworx-mcp-ny-omig-exclusions.md), [page](https://verifymcp.io/servers/pipeworx-io-ny-omig-exclusions/pipeworx-mcp-ny-omig-exclusions)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ny-omig-exclusions`
- 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-ny-omig-exclusions).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 621 tokens (~310/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**: 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 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.

## Install

### How do I install the Ny Omig Exclusions MCP server?

Ny Omig Exclusions runs locally as an npm package, launched with npx -y @pipeworx/mcp-ny-omig-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-ny-omig-exclusions -- npx -y @pipeworx/mcp-ny-omig-exclusions
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-ny-omig-exclusions -- npx -y @pipeworx/mcp-ny-omig-exclusions
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ny-omig-exclusions --command npx --arg -y --arg @pipeworx/mcp-ny-omig-exclusions
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-ny-omig-exclusions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ny-omig-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 82, +1)

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

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −14)

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

### 2026-11-01 (score 80, +1)

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

### 2026-10-30 (score 79, +1)

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

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

First indexed and scored.

## MCP tools (2)

### `ny_omig_check_exclusion` (~358 tokens)

Is this healthcare provider barred from New York State's Medicaid program? Screens a person or business name, an NPI, and/or a professional license number against the NY Office of the Medicaid Inspector General (OMIG) Medicaid exclusion list — the state-level counterpart to the federal HHS OIG LEIE (see the leie pack) for New York specifically. Answers "is this provider excluded from NY Medicaid", "check this NPI against the OMIG exclusion list", or pre-payment/credentialing screening for a NY 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 or address to tell same-named providers apart. Returns provider type and exclusion effective date for every match; OMIG's published data does not include an exclusion reason or statutory authority (unlike the federal LEIE), and the response says so. Pass npi or license to turn a name lead into an identification. Sourced from NY OMIG, keyless.

Input parameters:

- `license` (string): NY professional license/registration number, if known (e.g. pharmacy or physician license). 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". 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.

### `ny_omig_exclusion_coverage` (~202 tokens)

What the NY OMIG Medicaid exclusion data covers and how current it is: total exclusions held, how many carry an NPI or license number, how many distinct provider types appear, the oldest and newest exclusion dates, and OMIG's own "data last updated" date for the copy this pack serves. Use to check the screening data is fresh enough to rely on before a compliance decision, and to see the one-line note on what OMIG does NOT publish (exclusion reason/authority). 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 ~9,100-row list, not a page — answers "how many NY OMIG exclusions took effect in 2025". The response names the date field counted (excluded_since, OMIG's exclusion effective date). Sourced from NY OMIG, keyless.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### What is the Ny Omig Exclusions MCP server?

Ny Omig Exclusions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ny-omig-exclusions. New York State OMIG Medicaid provider exclusion screening, fleet #2788. This page covers its npm package (@pipeworx/mcp-ny-omig-exclusions).

### Is the Ny Omig Exclusions MCP server safe to use?

Ny Omig Exclusions scores 82 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 Ny Omig Exclusions MCP server expose?

Ny Omig Exclusions exposes 2 tools: ny_omig_check_exclusion, ny_omig_exclusion_coverage. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Is the Ny Omig Exclusions MCP server still maintained?

Ny Omig 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 Ny Omig Exclusions MCP server under?

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