MCP.Market

Nj Medical Exclusions MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/nj-medical-exclusions·v0.2.1

New Jersey Department of the Treasury Ineligible Provider List (Medical category) screening…

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Nj Medical Exclusions yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Nj Medical Exclusions tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Nj Medical Exclusions compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
201 ms
faster than 63% of 30,031 servers

Release history: 3 versions in the registry since 2026-10-19, latest 2026-11-03, typically one every 10 days.

Install Nj Medical Exclusions in Claude Code, Cursor or VS Code

claude mcp add --transport http nj-medical-exclusions https://gateway.pipeworx.io/nj-medical-exclusions/mcp
Add to Cursor

What the publisher says

From the Nj Medical Exclusions repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/nj-medical-exclusions

Screens a provider or business name, an NPI, or a Vendor ID against New Jersey's Medicaid provider exclusion/debarment list — the state-level counterpart to the federal HHS OIG LEIE for New Jersey specifically, and the sibling of ny-omig-exclusions, ca-medical-exclusions, tx-medical-exclusions, fl-medical-exclusions, pa-medical-exclusions, ga-medical-exclusions and oh-medical-exclusions.

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

Tools

provider or business against the list. An NPI or Vendor ID match is an IDENTIFICATION; a name match is a CANDIDATE lead only (no date of birth in this data). Every match carries the published action (Debarment, Suspension, or Disqualification), the reason code/label, the debarring department/agency, and a currentlyexcluded flag DERIVED from the expiration date and permanent-debarment flag — null with statusunknown:true when neither signal is present, never a guess.

  • njmedicalcheckexclusion(name?, npi?, vendorid?, limit?) — screens a

arguments, reports total rows, how many are currently excluded vs. ended vs. status-unknown, how many carry an NPI or Vendor ID, the distinct action types, and the oldest/newest effective dates. With year or a date range, counts how many exclusions took effect in that window (counted by effective_date, over the whole list, not a page).

  • njmedicalexclusioncoverage(year?, startdate?, end_date?) — with no

Auth

Keyless.

Data sources

Services — Ineligible Provider List (Medical) — the state's debarment, suspension, and disqualification notices for entities and individuals excluded from the New Jersey Medicaid program. No login, no CAPTCHA.

  • New Jersey Department of the Treasury, Division of Revenue and Enterprise

Notes

go back to 1976 and include providers whose debarment/suspension/ disqualification has since expired or been lifted.

  • This is the "ever excluded" file, not "currently excluded only." Rows

and a home (Individual) street/city/state/ZIP for every row; neither is baked or served here, matching the field set the seven precedent state exclusion packs serve.

  • No home address is served. The upstream carries both a business (Firm)

publish a single current-status field. Only a minority of rows carry an expiration date, and the Permanent Debarment flag is Y/N/blank. A row with neither signal reports status_unknown:true rather than an assumed still-active status.

  • currentlyexcluded is derived, not published.** New Jersey does not

this dataset's Individual Name field is Treasury's own combined display string ("LAST, FIRST MIDDLE (TITLE)"), with no separate first/last columns. Matching works on the combined string and the Firm Name field.

  • No parsed first/last name split — unlike the TX/PA/NY precedent packs,

match is the more common identification path.

  • Vendor ID is sparse — populated on a small minority of rows; an NPI

carries an implausible year ("4014"), kept and reported as published rather than silently corrected.

  • One known upstream data-entry artifact: a single row's effective date

and rebuilds src/nj-ips-index-data.ts; re-run periodically and recommit. dataasof on every response says how stale the baked copy is.

  • Refreshed by scripts/bake-index.mjs, which re-fetches the published file

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "nj-medical-exclusions": {
      "url": "https://gateway.pipeworx.io/nj-medical-exclusions/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Nj Medical Exclusions: common questions

Is Nj Medical Exclusions MCP server safe?
Mostly: it is graded B (73/100). Read the Nj Medical Exclusions safety report
How do I install Nj Medical 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 Nj Medical Exclusions need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Nj Medical Exclusions maintained?
The last commit was 16 days ago (2026-10-19). The latest release is v0.2.1.
Is Nj Medical Exclusions up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Nj Medical Exclusions compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 201 ms (faster than 63% of 30,031 servers). Full comparison.

More from pipeworx-io →