Pillwise
REMOTE · API.PILLWISE.DEV
US medication lookup: drug search, forms and strengths, NDC/RxCUI, recalls, shortages.
Available components
Last scanned (17 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 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 Security77
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 804 tokens (~89/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 23 Oct 26 +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.
- 21 Oct 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.
- 19 Oct 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.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 70
First indexed and scored.
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 23 Oct 2026 · Probed https://api.pillwise.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pillwise.dev | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 284dde9f93ee39e0e0246d4a1bb45a6 |
| SANs: pillwise.dev, *.pillwise.dev | ||||||
| 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 secure
Validation of api.pillwise.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| pillwise.dev. | present | 2371 | 13 | Verified |
| api.pillwise.dev. | Verified address RRset verified with the apex keys |
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://api.pillwise.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.pillwise.dev/mcp | HTTPS enforced | 301 | https://api.pillwise.dev/mcp |
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 →
catalog_freshness Catalog freshness ~25
How current the catalog is: the snapshot served and when it was built.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_drug Get a drug ~79
The full record for a Pillwise drug id: names, ingredients, form, strength, packages and recalls.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots. |
| id | string | yes | A Pillwise drug id, like pw_d_…. |
No output schema declared.
No examples provided.
get_form_options Form and strength choices ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots. |
| id | string | yes | A Pillwise drug id from search, like pw_g_… or pw_d_…. |
No output schema declared.
No examples provided.
get_packages List packages ~70
The package NDCs that belong to a Pillwise drug id.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots. |
| id | string | yes | A Pillwise drug id, like pw_d_…. |
No output schema declared.
No examples provided.
list_recalls List recalls ~86
Drug recalls, filtered by at least one of ndc, drug_id or since.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_shortages List shortages ~63
Drug shortages, filtered by at least one of ndc or drug_id.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_id | string | – | A Pillwise drug id. |
| ndc | string | – | A package NDC. |
| status | string | – | Optional, like Current or Resolved. |
No output schema declared.
No examples provided.
lookup_ndc Look up an NDC ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots. |
| ndc | string | yes | Like 50580-488-10 or 50580048810. |
No output schema declared.
No examples provided.
lookup_rxcui Look up an RxCUI ~66
The clinical drug for an RxCUI.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Optional. Answer as of this day (YYYY-MM-DD) or instant (RFC 3339), within retained snapshots. |
| rxcui | string | yes | Digits, like 314076. |
No output schema declared.
No examples provided.
search_medications Search medications ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What the person typed, at least 3 characters, like "tylenol" or "vitamin d3". |
No output schema declared.
No examples provided.
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.
remote · api.pillwise.dev
claude mcp add --transport http dev-pillwise-pillwise 'https://api.pillwise.dev/mcp'
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.