Oh Medical Exclusions
NPM · @PIPEWORX/MCP-OH-MEDICAL-EXCLUSIONS · 2 COMPONENTS
Ohio Department of Medicaid (ODM) Provider Exclusion & Suspension List screening — fleet #3278…
Available components
Last scanned (5 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-oh-medical-exclusions). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 724 tokens (~362/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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 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-oh-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-oh-medical-exclusions |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-oh-medical-exclusions/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679642893 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:de86e29dd33c09fbbe065a4a54be0531b4bcfbcbbbe89480f25555342100742e3ea3a504a73247edbfd3d7db5806e4017c0c4069efd7d58fedd570ccf |
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 →
oh_medical_check_exclusion ~461
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum matches to return (default 10, max 50). |
| name | string | – | Provider or organization name to screen, e.g. "John Smith" or "Acme Home Health". Matched against the provider's individual name and organization name, any word order. |
| npi | string | – | The provider's 10-digit NPI, if known. An NPI match is an identification rather than a name lead — always pass it when known. |
| provider_id | string | – | ODM's own Provider ID, if known. A Provider ID match is an identification. |
No output schema declared.
No examples provided.
oh_medical_exclusion_coverage ~205
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Oh Medical Exclusions MCP server?
Oh Medical Exclusions runs locally as an npm package, launched with npx -y @pipeworx/mcp-oh-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-oh-medical-exclusions
claude mcp add pipeworx-io-oh-medical-exclusions -- npx -y @pipeworx/mcp-oh-medical-exclusions
What is the Oh Medical Exclusions MCP server?
Oh Medical Exclusions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/oh-medical-exclusions. Ohio Department of Medicaid (ODM) Provider Exclusion & Suspension List screening, fleet #3278… This page covers its npm package (@pipeworx/mcp-oh-medical-exclusions).
Is the Oh Medical Exclusions MCP server safe to use?
Oh 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 Oh Medical Exclusions MCP server expose?
Oh Medical Exclusions exposes 2 tools: oh_medical_check_exclusion, oh_medical_exclusion_coverage. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.
Is the Oh Medical Exclusions MCP server still maintained?
Oh 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 Oh Medical Exclusions MCP server under?
Oh 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.