Healthcare Exclusion Lookup MCP server
com.trystarrynightops/healthcare-exclusion-lookuptrystarrynightops.comstreamable-httpv1.0.8Scanned
Screen people and businesses against the HHS-OIG exclusion list (LEIE) by name or NPI.
4 tools: 2 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Healthcare Exclusion Lookup MCP server can do
The Healthcare Exclusion Lookup MCP server is published by trystarrynightops.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: screen_exclusion and screen_exclusions), but cannot delete data. 2 tools only read.
1 tool reads private data (exclusion_list_status).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.8.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
screen_exclusionScreens 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, M…1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...es or initials, suffixes (Jr, Sr, III), credentials (MD, RN), punctuation, hyphenated surna..."
Description, as the server wrote it 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.
Annotations the server declares
- title: Screen a name against the OIG exclusion list (LEIE)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
screen_exclusionsScreens 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 thresho…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Screen up to 25 names against the LEIE
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
check_npiValidates a 10-digit National Provider Identifier (check digit) and looks it up in the NPI field of the LEIE mirror.No findings
Why it is in this group
- The description's first verb is "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check an NPI against the LEIE
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
exclusion_list_statusReturns 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, entiti…Reads private dataNo findings
Why it is in this group
- The name "exclusion_list_status" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: LEIE data version and freshness
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://exclusions.trystarrynightops.com/mcp: tools/list returned 4 tools to an anonymous client, including screen_exclusion (write), screen_exclusions (write)
Findings
Matches of fixed checks, with the text they matched.
- Infoscreen_exclusion
The description mentions "credentials".
What this check looks forMatched text
description: "...es or initials, suffixes (Jr, Sr, III), credentials (MD, RN), punctuation, hyphenated surna..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.8. Values in angle brackets are yours to fill in.
claude mcp add --transport http healthcare-exclusion-lookup https://exclusions.trystarrynightops.com/mcpclaude mcp add --transport http healthcare-exclusion-lookup https://exclusions.trystarrynightops.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__healthcare-exclusion-lookup__check_npi",
"mcp__healthcare-exclusion-lookup__exclusion_list_status"
],
"ask": [
"mcp__healthcare-exclusion-lookup__screen_exclusion",
"mcp__healthcare-exclusion-lookup__screen_exclusions"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as healthcare-exclusion-lookup. Review it before you use it.
Capability tags behind 1 rule
- mcp__healthcare-exclusion-lookup__exclusion_list_status private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.trystarrynightops/healthcare-exclusion-lookup/verify?hash=2bd0af660c21c71624c3e5fd49c7efdea1f9cc1bd027a77e5a8a5abdb15fe08f" | jq -e '.changed == false'Pinned hash 2bd0af660c21, from Nov 20, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.trystarrynightops/healthcare-exclusion-lookup/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.trystarrynightops/healthcare-exclusion-lookup)Source: MCP Registry. Synced Nov 20, 2026, 00:17 UTC.
Healthcare Exclusion Lookup MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Healthcare Exclusion Lookup MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Healthcare Exclusion Lookup MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Healthcare Exclusion Lookup MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Healthcare Exclusion Lookup MCP server have?
- 4 tools: 2 write, 2 read. screen_exclusion, screen_exclusions, check_npi and exclusion_list_status.
Does the Healthcare Exclusion Lookup MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Healthcare Exclusion Lookup MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Healthcare Exclusion Lookup MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.