# Pillwise (remote · api.pillwise.dev)

US medication lookup: drug search, forms and strengths, NDC/RxCUI, recalls, shortages.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `api.pillwise.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-pillwise-pillwise/api.md), [page](https://verifymcp.io/servers/dev-pillwise-pillwise/api)

## Channel facts

- Endpoint: `https://api.pillwise.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-10-23.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 804 tokens (~89/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Pillwise MCP server?

Pillwise is a hosted endpoint at https://api.pillwise.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 dev-pillwise-pillwise 'https://api.pillwise.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-pillwise-pillwise": {
      "url": "https://api.pillwise.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-pillwise-pillwise": {
      "type": "http",
      "url": "https://api.pillwise.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-pillwise-pillwise]
url = "https://api.pillwise.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-pillwise-pillwise": {
      "type": "remote",
      "url": "https://api.pillwise.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-pillwise-pillwise --url 'https://api.pillwise.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-pillwise-pillwise:
    url: "https://api.pillwise.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-pillwise-pillwise": {
      "Transport": "http",
      "Url": "https://api.pillwise.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-pillwise-pillwise -t streamable-http -u 'https://api.pillwise.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-pillwise-pillwise": {
      "type": "http",
      "url": "https://api.pillwise.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-10-23 (score 73, +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-10-21 (score 72, +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-10-19 (score 71, +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-10-18 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-17 (score 70)

First indexed and scored.

## MCP tools (9)

### `search_medications` (~118 tokens)

Search medications

Typeahead search by what a person calls a medication: brand, ingredient or everyday name. Returns brand and ingredient groups in the order a person would pick, not packages.

Input parameters:

- `as_of` (string): Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots.
- `limit` (integer): Hits to return (default 10).
- `query` (string, required): What the person typed, at least 3 characters, like "tylenol" or "vitamin d3".

### `get_form_options` (~98 tokens)

Form and strength choices

The forms (tablet, liquid, patch…) and strengths a medication comes in, with labels for people and values to send back. Use the id from a search hit.

Input parameters:

- `as_of` (string): Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots.
- `id` (string, required): A Pillwise drug id from search, like pw_g_… or pw_d_….

### `get_drug` (~79 tokens)

Get a drug

The full record for a Pillwise drug id: names, ingredients, form, strength, packages and recalls.

Input parameters:

- `as_of` (string): Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots.
- `id` (string, required): A Pillwise drug id, like pw_d_….

### `get_packages` (~70 tokens)

List packages

The package NDCs that belong to a Pillwise drug id.

Input parameters:

- `as_of` (string): Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots.
- `id` (string, required): A Pillwise drug id, like pw_d_….

### `lookup_ndc` (~125 tokens)

Look up an NDC

The package and drug for an NDC: 11 digits, 10 with hyphens (4-4-2, 5-3-2 or 5-4-1), or a product NDC. A bare 10-digit code is matched only as listed; no padding is guessed.

Input parameters:

- `as_of` (string): Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots.
- `ndc` (string, required): Like 50580-488-10 or 50580048810.

### `lookup_rxcui` (~66 tokens)

Look up an RxCUI

The clinical drug for an RxCUI.

Input parameters:

- `as_of` (string): Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots.
- `rxcui` (string, required): Digits, like 314076.

### `list_recalls` (~86 tokens)

List recalls

Drug recalls, filtered by at least one of ndc, drug_id or since.

Input parameters:

- `drug_id` (string): A Pillwise drug id.
- `ndc` (string): A package or product NDC.
- `since` (string): Recalls on or after this day, YYYY-MM-DD.
- `status` (string): Optional, like Ongoing or Terminated.

### `list_shortages` (~63 tokens)

List shortages

Drug shortages, filtered by at least one of ndc or drug_id.

Input parameters:

- `drug_id` (string): A Pillwise drug id.
- `ndc` (string): A package NDC.
- `status` (string): Optional, like Current or Resolved.

### `catalog_freshness` (~25 tokens)

Catalog freshness

How current the catalog is: the snapshot served and when it was built.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-pillwise-pillwise/api#diagnostics

## Score history

- 2026-10-23: 73
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 70
- 2026-10-17: 70

## Common questions

### What is the Pillwise MCP server?

Pillwise is an MCP server listed in the public MCP registry as dev.pillwise/pillwise. US medication lookup: drug search, forms and strengths, NDC/RxCUI, recalls, shortages. This page covers its hosted endpoint (https://api.pillwise.dev/mcp).

### Is the Pillwise MCP server safe to use?

Pillwise scores 73 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 Pillwise MCP server expose?

Pillwise exposes 9 tools: search_medications, get_form_options, get_drug, get_packages, lookup_ndc, and 4 more. Their descriptions and schemas cost roughly 730 tokens of context every time the server is loaded.

### Does the Pillwise MCP server require authentication?

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

### Is the Pillwise MCP server still maintained?

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

## Links

- Remote endpoint: https://api.pillwise.dev/mcp
- Authorisation metadata: https://api.pillwise.dev/.well-known/oauth-protected-resource/mcp
- Website: https://pillwise.dev/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-pillwise-pillwise/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-pillwise-pillwise/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-pillwise-pillwise/api