# Fl Medical Exclusions (npm · @pipeworx/mcp-fl-medical-exclusions)

Florida AHCA Medicaid Sanctioned Providers screening — check a provider name, NPI, Florida license…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/fl-medical-exclusions-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/fl-medical-exclusions-mcp)
- npm · `@pipeworx/mcp-fl-medical-exclusions`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/pipeworx-mcp-fl-medical-exclusions.md), [page](https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/pipeworx-mcp-fl-medical-exclusions)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-fl-medical-exclusions`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fl-medical-exclusions).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 825 tokens (~412/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fl Medical Exclusions MCP server?

Fl Medical Exclusions runs locally as an npm package, launched with npx -y @pipeworx/mcp-fl-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.

### Claude

```bash
claude mcp add pipeworx-io-fl-medical-exclusions -- npx -y @pipeworx/mcp-fl-medical-exclusions
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-fl-medical-exclusions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fl-medical-exclusions"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-fl-medical-exclusions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fl-medical-exclusions"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-fl-medical-exclusions -- npx -y @pipeworx/mcp-fl-medical-exclusions
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-fl-medical-exclusions": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-fl-medical-exclusions"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-fl-medical-exclusions --command npx --arg -y --arg @pipeworx/mcp-fl-medical-exclusions
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-fl-medical-exclusions:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-fl-medical-exclusions"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-fl-medical-exclusions": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-fl-medical-exclusions"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-fl-medical-exclusions -t stdio -c npx -a -y @pipeworx/mcp-fl-medical-exclusions
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-fl-medical-exclusions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-fl-medical-exclusions"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 79, +1)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `fl_medical_check_exclusion` (~512 tokens)

Is this healthcare provider excluded from, or sanctioned by, the Florida Medicaid program? Screens a person or business name, an NPI, a Florida license number, and/or a nine-digit Florida Medicaid provider number against the Florida Agency for Health Care Administration (AHCA) Medicaid Sanctioned Providers final-order list — the state-level counterpart to the federal HHS OIG LEIE (see the leie pack) for Florida specifically, and the sibling of ny_omig_check_exclusion (New York), ca_medical_check_exclusion (California) and tx_medical_check_exclusion (Texas). Answers "is this provider excluded from Florida Medicaid", "check this NPI against the Florida AHCA sanctions list", or pre-payment/credentialing screening for a Florida Medicaid provider. An NPI, license-number or Medicaid-provider-number match is an IDENTIFICATION; a name match — even an exact one — is a CANDIDATE lead only, since AHCA publishes no date of birth. The list is one row per sanction ORDER and most orders are fines or corrective action plans, which are NOT exclusions: every match carries sanction_class and is_participation_exclusion, and only a SUSPENSION (1-year preclusion) or TERMINATION (20-year preclusion) is reported as an exclusion. Each match also carries the Rule 59G-9.070 violation codes with AHCA's published descriptions, the fine amount, case numbers, and a DERIVED nominal end date (AHCA publishes no reinstatement date). Sourced from AHCA's Public Records final-orders search, keyless.

Input parameters:

- `license` (string): Florida professional or facility license number, if known, e.g. "ME81509" or "11075". A license match is an identification.
- `limit` (number): Maximum matching orders to return (default 10, max 50). Exclusion orders sort before fines within each tier, newest first.
- `medicaid_provider_number` (string): Nine-digit Florida Medicaid provider number, if known (leading zeros optional). A match is an identification.
- `name` (string): Provider or business name to screen, e.g. "John Smith" or "Acme Home Health Inc". Matched against the provider name on each order, 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.

### `fl_medical_exclusion_coverage` (~255 tokens)

What the Florida AHCA Medicaid Sanctioned Providers data covers and how current it is: total sanction final orders, how many are participation exclusions (suspensions/terminations) vs. fines and corrective action plans, distinct providers, how many orders carry an NPI, license or Medicaid provider number, the violation-code counts with AHCA's published key, the oldest and newest sanction dates, and when this pack's copy was captured. Use to check the screening data is fresh enough to rely on before a compliance decision, and to read the notes on the sanction-vs-exclusion distinction and the derived end dates. Pass year (e.g. 2025) or start_date/end_date to instead COUNT orders by sanction_date in that year or range, counted over the whole 7,000+ row list, not a page — answers "how many Florida Medicaid exclusions took effect in 2025". Returns participation_exclusion_count (suspensions + terminations only — the real exclusions) separately from all_sanction_orders_count (which also includes fines/CAPs, not exclusions); the response says which is which. Sourced from AHCA's Public Records final-orders search, keyless.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/pipeworx-mcp-fl-medical-exclusions#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Fl Medical Exclusions MCP server?

Fl Medical Exclusions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fl-medical-exclusions. Florida AHCA Medicaid Sanctioned Providers screening, check a provider name, NPI, Florida license… This page covers its npm package (@pipeworx/mcp-fl-medical-exclusions).

### Is the Fl Medical Exclusions MCP server safe to use?

Fl 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 Fl Medical Exclusions MCP server expose?

Fl Medical Exclusions exposes 2 tools: fl_medical_check_exclusion, fl_medical_exclusion_coverage. Their descriptions and schemas cost roughly 767 tokens of context every time the server is loaded.

### Is the Fl Medical Exclusions MCP server still maintained?

Fl 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 Fl Medical Exclusions MCP server under?

Fl 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-fl-medical-exclusions
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-fl-medical-exclusions
- Repository: https://github.com/pipeworx-io/mcp-fl-medical-exclusions
- Website: https://pipeworx.io/packs/fl-medical-exclusions
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/pipeworx-mcp-fl-medical-exclusions.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/pipeworx-mcp-fl-medical-exclusions.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-fl-medical-exclusions/pipeworx-mcp-fl-medical-exclusions