Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Il Medical Exclusions

NPM · @PIPEWORX/MCP-IL-MEDICAL-EXCLUSIONS · 2 COMPONENTS

Illinois Medicaid provider sanctions screening: the Illinois Department of Healthcare and Family…

81 Trust /100

Last scanned (7 hours ago)

Scores higher than 69% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-il-medical-exclusions). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 583 tokens (~291/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

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

  • 3 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 2 Nov 26 +1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: unverified → 0.10 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 79

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-il-medical-exclusions@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-il-medical-exclusions
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-il-medical-exclusions/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637414214
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9bd733a74e3ecc77ffb04a47cb73d8af092ad6814ea18485d8e3737e24f2405673821bc258f3cfcef117c73264050bfad0046727a37b10f125a924ac5

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~525 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
il_medical_check_exclusion ~355

Is this healthcare provider sanctioned or excluded from the Illinois Medicaid program? Screens a person or business name, an NPI, and/or a license number against the Illinois Department of Healthcare and Family Services (HFS) Office of Inspector General Provider Sanctions list: the state-level counterpart to the federal HHS OIG LEIE (leie pack) for Illinois, and sibling of tx_medical_check_exclusion, ny_omig_check_exclusion, ca_medical_check_exclusion and fl_medical_check_exclusion. Answers "is this provider barred from Illinois Medicaid", "check this NPI against the Illinois sanctions list", or pre-payment/credentialing screening for an Illinois Medicaid provider. An NPI or license-number match is an IDENTIFICATION; a name match, even an exact one, is a CANDIDATE lead only (the list has no date of birth). Each match carries the action type (Terminated, Barred, Exclusion, Suspended, Voluntary Withdrawal), the action date, provider type and any affiliated business. The response leads with counts by action type. No street addresses are served. Sourced from the Illinois HFS OIG, keyless.

NameTypeReqDescription
licensestring–Illinois professional license number, if known. A license match is an identification.
limitnumber–Maximum matches to return (default 10, max 50).
namestring–Provider or business name to screen, e.g. "Alrifai Tamer" or "Royal Transportation". Any word order.
npistring–The provider's 10-digit NPI, if known. An NPI match is an identification. Always pass it when known.

No output schema declared.

No examples provided.

il_medical_exclusion_coverage ~170

What the Illinois HFS OIG Provider Sanctions list covers and how current it is: total rows, counts by action type (Terminated, Barred, Exclusion, Suspended, Voluntary Withdrawal), how many carry an NPI or license number, oldest and newest action date, and the capture date. Use to check the screening data is fresh enough before a compliance decision. Pass year (e.g. 2025) or start_date/end_date to instead COUNT how many sanction actions have an action date in that year or range, counted over the whole list rather than a page, with the count split by action type. The response names the date field counted (action_date, HFS's Action Date). Sourced from the Illinois HFS OIG, keyless.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Il Medical Exclusions MCP server?

Il Medical Exclusions runs locally as an npm package, launched with npx -y @pipeworx/mcp-il-medical-exclusions. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-il-medical-exclusions

# add to Claude Code
claude mcp add pipeworx-io-il-medical-exclusions -- npx -y @pipeworx/mcp-il-medical-exclusions
Common questions

What is the Il Medical Exclusions MCP server?

Il Medical Exclusions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/il-medical-exclusions. Illinois Medicaid provider sanctions screening: the Illinois Department of Healthcare and Family… This page covers its npm package (@pipeworx/mcp-il-medical-exclusions).

Is the Il Medical Exclusions MCP server safe to use?

Il Medical Exclusions scores 81 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 Il Medical Exclusions MCP server expose?

Il Medical Exclusions exposes 2 tools: il_medical_check_exclusion, il_medical_exclusion_coverage. Their descriptions and schemas cost roughly 525 tokens of context every time the server is loaded.

Is the Il Medical Exclusions MCP server still maintained?

Il Medical 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 Il Medical Exclusions MCP server under?

Il Medical 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.