
Mi Medical Exclusions MCP server
online · 100% uptimeMichigan Medicaid provider sanctions screening: the Michigan Department of Health and Human…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Mi Medical Exclusions yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Mi Medical Exclusions tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Mi 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
- 263 ms
- faster than 53% of 30,031 servers
Release history: 3 versions in the registry since 2026-10-22, latest 2026-11-03, typically one every 7 days.
Install Mi Medical Exclusions in Claude Code, Cursor or VS Code
claude mcp add --transport http mi-medical-exclusions https://gateway.pipeworx.io/mi-medical-exclusions/mcp
What the publisher says
From the Mi Medical Exclusions repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/mi-medical-exclusions
Michigan Medicaid provider sanctions screening. Check a provider by name, NPI or license number against the Michigan Department of Health and Human Services (MDHHS) List of Sanctioned Providers, the state-level counterpart to the federal HHS OIG LEIE (leie pack) and sibling of il-medical-exclusions, tx-medical-exclusions, ny-omig-exclusions, ca-medical-exclusions and fl-medical-exclusions.
Part of Pipeworx — an MCP gateway connecting AI agents to 1866+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
An NPI or license match is an identification; a name match, even an exact one, is a candidate lead only (no date of birth is published). The response leads with counts by sanction source, then the matches. Each match carries the sanction date and source, a second sanction date and source where present (often the action being lifted), provider category and MDHHS's reason text. A no-match names the filters tried.
- mimedicalcheck_exclusion(name?, npi?, license?, limit?): screens a provider.
sanction source, individuals vs businesses, NPI, license and reason coverage, oldest and newest sanction date and the list's own publication date. With year or a date range it counts sanctions in that window over the whole list, split by sanction source. The counted field is sanction_date (the first Sanction Date column), never the second date; the response says so.
- mimedicalexclusioncoverage(year? | startdate? end_date?): totals by
Auth
Keyless.
Data source
Michigan Department of Health and Human Services, List of Sanctioned Providers (4,111 rows at capture). It merges sanctions from MDHHS, its Office of Inspector General, Licensing and Regulatory Affairs, the former DCH and HHS; each row names its source. dataasof is the publication date printed on the list itself.
What the list does and does not say
are Social Security Act section numbers such as 1128(a)(1), not plain language.
- MDHHS says the list is built partly from outside sources and may be incomplete.
- The reason field is free text and is blank on about 60% of rows; some values
usually stays with a second date (for example "Summary Suspension Terminated"), so read reason and secondsanctiondate together before calling anyone currently sanctioned.
- No date of birth and no reinstatement flag. When an action was lifted the row
Personal data
The list has a City column. It is kept for businesses only; for any individual it is dropped at ingest, and a test asserts it. No street address or date of birth is published or served. This follows the standing rule for state exclusion packs: name plus the sanction record plus the date, never an address for an individual.
How the data is served
The publication is a bulk spreadsheet, not a query service. It is copied by scripts/bake-index.mjs, registered in workers/gateway/src/pack-baked-indexes.json, uploaded to KV at deploy and injected as args._bakedIndex (never a module-scope import; fleet #2754). A missing or malformed injection throws loudly rather than answering "not found".
Refresh: re-run node mcps/mi-medical-exclusions/scripts/bake-index.mjs and commit; there is no scheduled refresh yet, same as the sibling baked packs.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"mi-medical-exclusions": {
"url": "https://gateway.pipeworx.io/mi-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.
Mi Medical Exclusions: common questions
- Is Mi Medical Exclusions MCP server safe?
- Mostly: it is graded B (73/100). Read the Mi Medical Exclusions safety report
- How do I install Mi 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 Mi Medical Exclusions need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Mi Medical Exclusions maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v0.2.1.
- Is Mi Medical Exclusions up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Mi 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 263 ms (faster than 53% of 30,031 servers). Full comparison.