
Ny Omig Exclusions MCP server
online · 100% uptimeNew York State OMIG Medicaid provider exclusion screening — fleet #2788.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Ny Omig Exclusions yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Ny Omig Exclusions tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Ny Omig Exclusions compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 187 ms
- faster than 66% of 30,031 servers
Release history: 5 versions in the registry since 2026-10-07, latest 2026-11-03, typically one every 6 days.
Install Ny Omig Exclusions in Claude Code, Cursor or VS Code
claude mcp add --transport http ny-omig-exclusions https://gateway.pipeworx.io/ny-omig-exclusions/mcp
What the publisher says
From the Ny Omig Exclusions repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/ny-omig-exclusions
New York State OMIG Medicaid provider exclusion screening — check a provider by name, NPI or license number against the NY Office of the Medicaid Inspector General's exclusion list, the state-level counterpart to the federal HHS OIG LEIE (leie pack) for New York specifically.
Part of Pipeworx — an MCP gateway connecting AI agents to 1784+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
provider against the ~9,100-row NY OMIG exclusion list. 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 OMIG's list carries no date of birth or address to tell same-named providers apart.
- nyomigcheck_exclusion(name?, npi?, license?, limit?) — screens a
NPI or license number, provider-type diversity, the oldest/newest exclusion date, and OMIG's own "data last updated" date for the baked copy this pack serves.
- nyomigexclusion_coverage() — total exclusions held, how many carry an
Auth
Keyless.
Data sources
exclusion list as tab-delimited text (provider name, license number, NPI, provider type, exclusion effective date). No JSON/REST endpoint exists; this is the cleanest of OMIG's export formats (vs. a 6.5MB HTML "formatted list" for the same ~9,100 rows).
- — the full
HTML page, fetched only for its cheap "Data was last updated" banner (45KB vs. 6.5MB for the full formatted list).
- — the "last 30 days"
search tool (up to 5 names at once), linked in every response as onlinesearchurl for a caller who wants to verify directly.
- — OMIG's own online
Why this is baked, not a live proxy
OMIG publishes the list only as flat files. Per root CLAUDE.md's standing rule for exactly this shape, the table (~9,117 rows, ~1.3MB as generated TypeScript) is baked by scripts/bake-index.mjs into src/ny-omig-index-data.ts, registered in workers/gateway/src/pack-baked-indexes.json, uploaded to KV at deploy, and injected into every call as args._bakedIndex — never a static module-scope import (fleet #2754: six packs doing that put ~48MB of retained heap into every gateway isolate and cost about one call in four as a Cloudflare 1102). A missing or malformed injection throws loudly rather than answering "not found" — see src/index.test.ts.
Re-run node mcps/ny-omig-exclusions/scripts/bake-index.mjs periodically to refresh the copy and recommit; dataasof on every response says how stale it is relative to OMIG's own "last updated" banner, so staleness is visible rather than silent.
What this data does NOT include
Every OMIG export — tab-delimited, Excel, and the HTML formatted list — carries only provider name, license number, NPI, provider type and the exclusion effective date. There is no exclusion reason, statutory authority or case citation in this data, unlike the federal LEIE's statutory exclusion-type code. Per-record detail, if OMIG holds any, sits behind an ASP.NET VIEWSTATE postback tied to a freshly-loaded search session rather than a stable queryable endpoint, and was not pursued for this first cut. Every response says this plainly rather than inventing a field OMIG does not publish.
Reachability
Verified live 2026-10-07 from both a laptop curl and a throwaway wrangler dev --remote Worker on the prod account: identical 200 / 535,395 bytes from the Cloudflare edge on tabdelimited.aspx. Unlike oklahoma-code / utah-code / new-hampshire-code, this host needs no Supabase egress relay.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Ny Omig Exclusions: common questions
- Is Ny Omig Exclusions MCP server safe?
- Mostly: it is graded B (77/100). Read the Ny Omig Exclusions safety report
- How do I install Ny Omig Exclusions?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Ny Omig Exclusions need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Ny Omig Exclusions maintained?
- The last commit was 27 days ago (2026-10-07). The latest release is v0.2.1.
- Is Ny Omig Exclusions up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Ny Omig Exclusions compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 187 ms (faster than 66% of 30,031 servers). Full comparison.