MCP server exposing 2 tools for oh-medical-exclusions.
This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.
POST https://gateway.pipeworx.io/oh-medical-exclusions/mcp
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}oh_medical_check_exclusion — Is this healthcare provider excluded from, or suspended from, the Ohio Medicaid program? Screens a person or organization name, an NPI, and/or an ODM Provider ID against the Ohio Department of Medicaid (ODM) Provider Exclusion & Suspension List — the state-level counterpart to the federal HHS OIG LEIE (see the leie pack) for Ohio specifically, and the sibling of ny_omig_check_exclusion (New York), ca_medical_check_exclusion (California), tx_medical_check_exclusion (Texas), fl_medical_check_exclusion (Florida), pa_medical_check_exclusion (Pennsylvania) and ga_medical_check_exclusion (Georgia). Answers "is this provider excluded from Ohio Medicaid", "check this NPI against the Ohio ODM exclusion list", or pre-payment/credentialing screening for an Ohio Medicaid provider. An NPI or Provider ID match is an IDENTIFICATION (both are exact identifiers ODM assigns/records, and either can be a comma-joined list on one row when a provider is excluded under multiple registrations); a name match — even an exact one — is a CANDIDATE lead only, since this list carries no date of birth. Every match carries ODM's own Status field (Excluded, Suspended, or occasionally Terminated/blank) and a currently_excluded flag DERIVED from it — null with status_unknown:true when the status is not a recognized Excluded/Suspended value, rather than a guess. Pass npi or provider_id to turn a name lead into an identification. Sourced from the Ohio ODM Provider Exclusion & Suspension List, keyless.oh_medical_exclusion_coverage — What the Ohio ODM exclusion/suspension data covers and how current it is: total rows (individuals plus organizations), how many are currently excluded/suspended vs. status-unknown, how many carry an NPI, and the oldest/newest exclusion effective date. Use to check the screening data is fresh enough to rely on before a compliance decision, and to see the one-line note on the status field's gaps. Pass year (e.g. 2025) or start_date/end_date to instead COUNT how many exclusions have an effective date in that year or range, counted over the whole 2,100+ row list, not a page — answers "how many Ohio ODM exclusions took effect in 2025". The response names the date field counted (action_date / ODM's Action Date — never date_added, which answers a different question and gives a different number). Sourced from the Ohio ODM Provider Exclusion & Suspension List, keyless.Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/oh-medical-exclusions/
Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io