# Healthcare Exclusion Lookup (remote · exclusions.trystarrynightops.com)

Screen people and businesses against the HHS-OIG exclusion list (LEIE) by name or NPI.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `exclusions.trystarrynightops.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-trystarrynightops-healthcare-exclusion-lookup/exclusions.md), [page](https://verifymcp.io/servers/com-trystarrynightops-healthcare-exclusion-lookup/exclusions)

## Channel facts

- Endpoint: `https://exclusions.trystarrynightops.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.8`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1072 tokens (~268/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Healthcare Exclusion Lookup MCP server?

Healthcare Exclusion Lookup is a hosted endpoint at https://exclusions.trystarrynightops.com/mcp, so there is nothing to install locally. 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 --transport http com-trystarrynightops-healthcare-exclusion-looku 'https://exclusions.trystarrynightops.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-trystarrynightops-healthcare-exclusion-looku": {
      "url": "https://exclusions.trystarrynightops.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-trystarrynightops-healthcare-exclusion-looku": {
      "type": "http",
      "url": "https://exclusions.trystarrynightops.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-trystarrynightops-healthcare-exclusion-looku]
url = "https://exclusions.trystarrynightops.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-trystarrynightops-healthcare-exclusion-looku": {
      "type": "remote",
      "url": "https://exclusions.trystarrynightops.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-trystarrynightops-healthcare-exclusion-looku --url 'https://exclusions.trystarrynightops.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-trystarrynightops-healthcare-exclusion-looku:
    url: "https://exclusions.trystarrynightops.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-trystarrynightops-healthcare-exclusion-looku": {
      "Transport": "http",
      "Url": "https://exclusions.trystarrynightops.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-trystarrynightops-healthcare-exclusion-looku -t streamable-http -u 'https://exclusions.trystarrynightops.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-trystarrynightops-healthcare-exclusion-looku": {
      "type": "http",
      "url": "https://exclusions.trystarrynightops.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 69, +1)

- [functional] Server version: 1.0.7 → 1.0.8

### 2026-11-19 (score 68, 0)

- [functional] Server version: 1.0.6 → 1.0.7

### 2026-11-18 (score 68, +1)

- [functional] Server version: 1.0.5 → 1.0.6
- [functional] Server version: 1.0.4 → 1.0.5

### 2026-11-16 (score 67, +1)

- [functional] Server version: 1.0.3 → 1.0.4

### 2026-11-15 (score 66, 0)

- [functional] Server version: 1.0.2 → 1.0.3

### 2026-11-14 (score 66, +1)

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

### 2026-11-13 (score 65, 0)

- [functional] Server version: 1.0.1 → 1.0.2

### 2026-11-12 (score 65, +1)

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

## MCP tools (4)

### `screen_exclusion` (~527 tokens)

Screen a name against the OIG exclusion list (LEIE)

Screens one person or business name against a mirrored copy of the HHS-OIG List of Excluded Individuals/Entities (LEIE), the list of people and businesses excluded from Medicare, Medicaid and other federal health care programs. Person names match in any word order, with or without middle names or initials, suffixes (Jr, Sr, III), credentials (MD, RN), punctuation, hyphenated surnames, common nicknames and one-letter typos; business names match without company-form words (LLC, Inc, PC) and with abbreviations and small typos. Returns ranked possible matches with score, name, general category and specialty, city, state, ZIP, NPI when present, exclusion type with its meaning, exclusion date and any waiver, or a no-match result at the threshold, plus the list's as-of date. Optional state, NPI and date-of-birth filters narrow common names.

Input parameters:

- `detail` (string): "summary" (default) returns the key fields; "full" adds UPIN, the exclusion kind and minimum period, and the middle-name comparison.
- `dob` (string): Optional date of birth, YYYY-MM-DD. Used only to report whether it matches each record ("matches", or "no DOB on file"); records whose date of birth does not match are left out and counted. The date…
- `limit` (integer): Maximum number of matches to return, 1 to 25 (default 5).
- `min_score` (number): Similarity threshold from 0.5 to 1.0 (default 0.85). 1.0 = same first and last name (or business name) after normalization; lower values return weaker possible matches.
- `name` (string, required): Person ("Jane Q. Doe", "Doe, Jane", "Jane Doe RN") or business ("Acme Home Health LLC") to screen.
- `npi` (string): Optional 10-digit National Provider Identifier. Records with a different NPI are left out and counted; records without an NPI (most of the list) are kept.
- `state` (string): Optional U.S. state filter: two-letter code ("OH") or name ("Ohio"). Records in other states are left out and counted; records with no state are kept. The LEIE address is the one at the time of exclu…
- `type` (string): Optional: "individual" for a person, "entity" for a business. Default: both.

### `screen_exclusions` (~276 tokens)

Screen up to 25 names against the LEIE

Screens up to 25 person or business names in one call against the same LEIE mirror as screen_exclusion and returns only the best possible match per name (or no match at the threshold) in compact form, with a summary count. When a state, npi or dob filter leaves out every record at or above the threshold, the result for that entry is no_match_after_filters and it shows the best record the filter left out. Each entry can be a name string or an object with name and optional state, npi and dob (YYYY-MM-DD).

Input parameters:

- `min_score` (number): Similarity threshold from 0.5 to 1.0 (default 0.85). 1.0 = same first and last name (or business name) after normalization; lower values return weaker possible matches.
- `names` (array, required): Names to screen (1 to 25), e.g. ["Jane Doe", {"name": "John Q. Public", "state": "TX", "dob": "1970-01-31"}, "Acme Home Health LLC"].
- `state` (string): Optional state filter applied to every name that does not set its own.
- `type` (string): Optional: "individual" for a person, "entity" for a business. Default: both.

### `check_npi` (~121 tokens)

Check an NPI against the LEIE

Validates a 10-digit National Provider Identifier (check digit) and looks it up in the NPI field of the LEIE mirror. Returns the excluded record(s) that carry it, or a not-on-list result. Most LEIE records have no NPI, so a not-on-list result does not show that a provider is not excluded.

Input parameters:

- `detail` (string): "full" adds UPIN and the exclusion kind and minimum period.
- `npi` (string, required): 10-digit NPI, e.g. "1234567893".

### `exclusion_list_status` (~72 tokens)

LEIE data version and freshness

Returns the version of the mirrored LEIE: OIG's last update date and the month the data runs through, the source file's timestamp, size and hash, record counts (individuals, entities, with NPI), the latest monthly supplement, and when the mirror was last built and last checked for updates.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-trystarrynightops-healthcare-exclusion-lookup/exclusions#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 68
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 64
- 2026-11-10: 64

## Common questions

### What is the Healthcare Exclusion Lookup MCP server?

Healthcare Exclusion Lookup is an MCP server listed in the public MCP registry as com.trystarrynightops/healthcare-exclusion-lookup. Screen people and businesses against the HHS-OIG exclusion list (LEIE) by name or NPI. This page covers its hosted endpoint (https://exclusions.trystarrynightops.com/mcp).

### Is the Healthcare Exclusion Lookup MCP server safe to use?

Healthcare Exclusion Lookup scores 69 out of 100 on VerifyMCP. 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 Healthcare Exclusion Lookup MCP server expose?

Healthcare Exclusion Lookup exposes 4 tools: screen_exclusion, screen_exclusions, check_npi, exclusion_list_status. Their descriptions and schemas cost roughly 996 tokens of context every time the server is loaded.

### Does the Healthcare Exclusion Lookup MCP server require authentication?

No. We connected to Healthcare Exclusion Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Healthcare Exclusion Lookup MCP server still maintained?

Healthcare Exclusion Lookup is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Healthcare Exclusion Lookup MCP server?

VerifyMCP ran 12 checks on Healthcare Exclusion Lookup, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Healthcare Exclusion Lookup: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://exclusions.trystarrynightops.com/mcp
- Website: https://exclusions.trystarrynightops.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-trystarrynightops-healthcare-exclusion-lookup/exclusions.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-trystarrynightops-healthcare-exclusion-lookup/exclusions/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-trystarrynightops-healthcare-exclusion-lookup/exclusions.json
- HTML version of this page: https://verifymcp.io/servers/com-trystarrynightops-healthcare-exclusion-lookup/exclusions
