Mi Medical Exclusions
NPM · @PIPEWORX/MCP-MI-MEDICAL-EXCLUSIONS · 2 COMPONENTS
Michigan Medicaid provider sanctions screening: the Michigan Department of Health and Human…
Available components
Last scanned (11 hours ago)
Scores higher than 69% of npm servers
Category Health and Science
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-mi-medical-exclusions). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 629 tokens (~314/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 Management23
- Stability observed for 7 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
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 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 29 Oct 26 78
First indexed and scored.
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-mi-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-mi-medical-exclusions |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-mi-medical-exclusions/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655436747 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dca23b64bf32818c14e809350bca89f7f213c4c318dd625eead6c5cbab5fc62bb586b7594778cc568b579b7a729aea6fbdbe474d68738397f538f655f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mi_medical_check_exclusion ~388
Is this healthcare provider sanctioned or excluded from the Michigan Medicaid program? Screens a person or business name, an NPI, and/or a license number against the Michigan Department of Health and Human Services (MDHHS) List of Sanctioned Providers, which merges sanctions from MDHHS, its Office of Inspector General, Licensing and Regulatory Affairs and HHS. State-level counterpart to the federal HHS OIG LEIE (leie pack) for Michigan, sibling of il_medical_check_exclusion, tx_medical_check_exclusion, ny_omig_check_exclusion and ca_medical_check_exclusion. Answers "is this provider on the Michigan Medicaid sanction list", "check this NPI against Michigan sanctions", or pre-payment/credentialing screening for a Michigan Medicaid provider. An NPI or license-number match is an IDENTIFICATION; a name match, even an exact one, is a CANDIDATE lead only (no date of birth is published). Each match carries the sanction date and source, a second sanction date and source where present (often the action being lifted), the provider category and MDHHS's free-text reason (blank on about 60% of rows). The response leads with counts by sanction source. City is served for businesses only; no street addresses. Sourced from MDHHS, keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| license | string | – | Michigan professional license number, if known. 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. "1st Priority Physical Therapy" or "Oshiyoye". Any word order. |
| npi | string | – | 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.
mi_medical_exclusion_coverage ~183
What the Michigan MDHHS List of Sanctioned Providers covers and how current it is: total rows, counts by sanction source (MDHHS, MDHHS-OIG, LARA, DCH, HHS), individuals vs businesses, how many carry an NPI, license number or reason, oldest and newest sanction date, and the list's own publication 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 sanctions have a sanction date in that year or range, counted over the whole list rather than a page, split by sanction source. The response names the date field counted (sanction_date, the first Sanction Date column, never the second date). Sourced from MDHHS, keyless.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Mi Medical Exclusions MCP server?
Mi Medical Exclusions runs locally as an npm package, launched with npx -y @pipeworx/mcp-mi-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-mi-medical-exclusions
claude mcp add pipeworx-io-mi-medical-exclusions -- npx -y @pipeworx/mcp-mi-medical-exclusions
What is the Mi Medical Exclusions MCP server?
Mi Medical Exclusions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mi-medical-exclusions. Michigan Medicaid provider sanctions screening: the Michigan Department of Health and Human… This page covers its npm package (@pipeworx/mcp-mi-medical-exclusions).
Is the Mi Medical Exclusions MCP server safe to use?
Mi 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 Mi Medical Exclusions MCP server expose?
Mi Medical Exclusions exposes 2 tools: mi_medical_check_exclusion, mi_medical_exclusion_coverage. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
Is the Mi Medical Exclusions MCP server still maintained?
Mi 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 Mi Medical Exclusions MCP server under?
Mi 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.