# Drug Shortage List MCP (remote · drug-shortage-list-mcp.lipmichal.workers.dev)

FDA drug shortage list: is a drug in shortage now, by name or NDC, with status and reason.

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

## Components

- remote · `drug-shortage-list-mcp.lipmichal.workers.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-drug-shortage-list-mcp/drug-shortage-list-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-drug-shortage-list-mcp/drug-shortage-list-mcp)

## Channel facts

- Endpoint: `https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 544 tokens (~136/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**: 53/100
  - Stability observed for 16 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 Drug Shortage List MCP server?

Drug Shortage List MCP is a hosted endpoint at https://drug-shortage-list-mcp.lipmichal.workers.dev/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 theluckystrike-drug-shortage-list-mcp 'https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-drug-shortage-list-mcp": {
      "url": "https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-drug-shortage-list-mcp": {
      "type": "http",
      "url": "https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-drug-shortage-list-mcp]
url = "https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-drug-shortage-list-mcp": {
      "type": "remote",
      "url": "https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-drug-shortage-list-mcp --url 'https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-drug-shortage-list-mcp:
    url: "https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-drug-shortage-list-mcp": {
      "Transport": "http",
      "Url": "https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-drug-shortage-list-mcp -t streamable-http -u 'https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-drug-shortage-list-mcp": {
      "type": "http",
      "url": "https://drug-shortage-list-mcp.lipmichal.workers.dev/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 74, +1)

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

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

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

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

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

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

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

### 2026-11-11 (score 70, +1)

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

### 2026-11-09 (score 69, +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-07 (score 68, +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.

### 2026-11-06 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `search_drug_shortages` (~186 tokens)

Search drug shortages

Is a drug in shortage now? Searches the FDA Drug Shortages database (via openFDA, updated daily) by generic name, brand name or active ingredient, for example "amoxicillin", "Adderall", "semaglutide", "lidocaine". Returns listings grouped by product with counts by status (Current, To Be Discontinued, Resolved) and availability (Available, Limited, Unavailable), shortage reasons, companies, presentations and dates. Your training data cannot know today's shortage list.

Input parameters:

- `drug` (string, required): Generic name, brand name or active ingredient, for example "amphetamine", "Adderall", "cefazolin".
- `max_presentations` (integer): Package listings to show per product, 1 to 100. Default 10.
- `status` (string): current, to_be_discontinued, resolved or all. Default all.

### `get_drug_shortage_by_ndc` (~101 tokens)

Get drug shortage by NDC

FDA shortage status for one National Drug Code, either a package NDC (0641-6059-01) or a product NDC (0641-6059), in the dashed form printed on the label. Returns the exact listing and related packages of the same product.

Input parameters:

- `ndc` (string, required): Dashed NDC, for example "0641-6059-01" or "0641-6059".

### `list_recent_drug_shortages` (~109 tokens)

List recent drug shortages

The FDA drug shortage list, most recently updated listings first. Defaults to status Current. Filter by therapeutic category, for example Anesthesia, Oncology, Pediatric, Psychiatry, Cardiovascular, Infectious Disease.

Input parameters:

- `limit` (integer): Listings to return, 1 to 100. Default 25.
- `status` (string): current, to_be_discontinued, resolved or all. Default current.
- `therapeutic_category` (string): FDA therapeutic category, for example "Oncology".

### `count_drug_shortages` (~77 tokens)

Count drug shortages

How many FDA drug shortage listings there are now, grouped by status, therapeutic_category, shortage_reason or drug (distinct products). Defaults to Current listings by therapeutic category.

Input parameters:

- `by` (string): Grouping. Default therapeutic_category.
- `status` (string): Status to count within, ignored when by is status. Default current.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-drug-shortage-list-mcp/drug-shortage-list-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 71
- 2026-11-14: 71
- 2026-11-13: 70
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68
- 2026-11-07: 68
- 2026-11-06: 67
- 2026-11-05: 67

## Common questions

### What is the Drug Shortage List MCP server?

Drug Shortage List MCP is listed in the public MCP registry as io.github.theluckystrike/drug-shortage-list-mcp. FDA drug shortage list: is a drug in shortage now, by name or NDC, with status and reason. This page covers its hosted endpoint (https://drug-shortage-list-mcp.lipmichal.workers.dev/mcp).

### Is the Drug Shortage List MCP server safe to use?

Drug Shortage List MCP scores 74 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 Drug Shortage List MCP server expose?

Drug Shortage List MCP exposes 4 tools: search_drug_shortages, get_drug_shortage_by_ndc, list_recent_drug_shortages, count_drug_shortages. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.

### Does the Drug Shortage List MCP server require authentication?

No. We connected to Drug Shortage List MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Drug Shortage List MCP server still maintained?

Drug Shortage List MCP 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 Drug Shortage List MCP server?

VerifyMCP ran 12 checks on Drug Shortage List MCP, 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 Drug Shortage List MCP: 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://drug-shortage-list-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/drug-shortage-list-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-drug-shortage-list-mcp/drug-shortage-list-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-drug-shortage-list-mcp/drug-shortage-list-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-drug-shortage-list-mcp/drug-shortage-list-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-drug-shortage-list-mcp/drug-shortage-list-mcp
