Nc Medical Exclusions
NPM · @PIPEWORX/MCP-NC-MEDICAL-EXCLUSIONS · 2 COMPONENTS
NC Medicaid (Division of Health Benefits, Office of Compliance and Program Integrity) State…
Available components
Last scanned (8 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-nc-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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 755 tokens (~377/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 +16
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 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-nc-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-nc-medical-exclusions |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-nc-medical-exclusions/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655663847 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:dd5dc6d868e3a9d7d25c863ebac912dfb05851de4b09d5775c9cca3cba68d0422ccdd724994af2219f9e9beecc32de46f039fc881e458e3532f5c8e98 |
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 →
nc_medical_check_exclusion ~501
Is this healthcare provider excluded from the North Carolina Medicaid program? Screens a person or business name, an NPI, and/or an atypical (non-NPI) Medicaid provider ID against NC Medicaid's (Division of Health Benefits, Office of Compliance and Program Integrity) State Excluded Providers List — the state-level counterpart to the federal HHS OIG LEIE (see the leie pack) for North Carolina 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), ga_medical_check_exclusion (Georgia), oh_medical_check_exclusion (Ohio) and nj_medical_check_exclusion (New Jersey). Answers "is this provider excluded from North Carolina Medicaid" or pre-payment/credentialing screening for an NC Medicaid provider. An NPI or atypical-ID match is an IDENTIFICATION (both are exact, provider-specific identifiers); a name match against the EXCLUDED ENTITY field — even an exact one — is a CANDIDATE lead only, since this list carries no date of birth to tell same-named providers apart. A name that matches only the OWNERSHIP field (not the excluded entity) comes back as ownership_only_match with excluded:false — NC Medicaid's own note says an owner/principal name is NOT itself excluded unless separately listed. This dataset is a CURRENT SNAPSHOT (no history of lifted exclusions), so every match is currently_excluded:true. Pass npi or atypical_id to turn a name lead into an identification. Sourced from the NC Medicaid State Excluded Providers List, keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| atypical_id | string | – | NC Medicaid's non-NPI "atypical" provider ID, if known (used for some providers instead of an NPI). A match is an identification. |
| limit | number | – | Maximum matches to return (default 10, max 50). |
| name | string | – | Provider or business name to screen, e.g. "Jane Doe" or "Acme Home Health LLC". Matched against the excluded entity name first, then the ownership field. |
| 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. |
No output schema declared.
No examples provided.
nc_medical_exclusion_coverage ~195
What the NC Medicaid State Excluded Providers List covers and how current it is: total rows, how many carry an NPI vs. an atypical (non-NPI) ID, the distinct exclusion reasons published (FEDERAL, STATE, OIG, and combinations), and the oldest/newest exclusion effective dates. Notes that this is a CURRENT SNAPSHOT (not an ever-excluded history) — a reinstated provider simply disappears from the next monthly file. 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 list, not a page — answers "how many NC Medicaid exclusions took effect in 2025". The response names the date field counted (effective_date — NC Medicaid's own EFFECTIVE DATE column). Sourced from the NC Medicaid State Excluded Providers List, keyless.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Nc Medical Exclusions MCP server?
Nc Medical Exclusions runs locally as an npm package, launched with npx -y @pipeworx/mcp-nc-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-nc-medical-exclusions
claude mcp add pipeworx-io-nc-medical-exclusions -- npx -y @pipeworx/mcp-nc-medical-exclusions
What is the Nc Medical Exclusions MCP server?
Nc Medical Exclusions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nc-medical-exclusions. NC Medicaid (Division of Health Benefits, Office of Compliance and Program Integrity) State… This page covers its npm package (@pipeworx/mcp-nc-medical-exclusions).
Is the Nc Medical Exclusions MCP server safe to use?
Nc 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 Nc Medical Exclusions MCP server expose?
Nc Medical Exclusions exposes 2 tools: nc_medical_check_exclusion, nc_medical_exclusion_coverage. Their descriptions and schemas cost roughly 696 tokens of context every time the server is loaded.
Is the Nc Medical Exclusions MCP server still maintained?
Nc 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 Nc Medical Exclusions MCP server under?
Nc 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.