Healthcare Exclusion Lookup
REMOTE · EXCLUSIONS.TRYSTARRYNIGHTOPS.COM
Screen people and businesses against the HHS-OIG exclusion list (LEIE) by name or NPI.
Available components
Last scanned (21 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
- Server version: 1.0.7 → 1.0.8 functional
- 19 Nov 26 0
- Server version: 1.0.6 → 1.0.7 functional
- 18 Nov 26 +1
- Server version: 1.0.5 → 1.0.6 functional
- Server version: 1.0.4 → 1.0.5 functional
- 16 Nov 26 +1
- Server version: 1.0.3 → 1.0.4 functional
- 15 Nov 26 0
- Server version: 1.0.2 → 1.0.3 functional
- 14 Nov 26 +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.
- 13 Nov 26 0
- Server version: 1.0.1 → 1.0.2 functional
- 12 Nov 26 +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.
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 21 Nov 2026 · Probed https://exclusions.trystarrynightops.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trystarrynightops.com | CN=WE1,O=Google Trust Services,C=US | 8 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | ad864ef774dbd7ea0e754251022a216f |
| SANs: trystarrynightops.com, exclusions.trystarrynightops.com, *.exclusions.trystarrynightops.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of exclusions.trystarrynightops.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| trystarrynightops.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://exclusions.trystarrynightops.com/mcp | Verified | 200 | |
| http (plaintext) | http://exclusions.trystarrynightops.com/mcp | Inconclusive | 405 |
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 →
check_npi Check an NPI against the LEIE ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | "full" adds UPIN and the exclusion kind and minimum period. |
| npi | string | yes | 10-digit NPI, e.g. "1234567893". |
No output schema declared.
No examples provided.
exclusion_list_status LEIE data version and freshness ~72
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_exclusion Screen a name against the OIG exclusion list (LEIE) ~527
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
screen_exclusions Screen up to 25 names against the LEIE ~276
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · exclusions.trystarrynightops.com
claude mcp add --transport http com-trystarrynightops-healthcare-exclusion-looku 'https://exclusions.trystarrynightops.com/mcp'
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.