io.usefulapi/dailymed
REMOTE · DAILYMED.USEFULAPI.IO · SCANNED OCT 4
Search DailyMed drug labels, SPLs, NDCs and packaging.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1443 tokens (~120/item across 12 items; 12 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.usefulapi/dailymed MCP server?
io.usefulapi/dailymed is a hosted endpoint at https://dailymed.usefulapi.io/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 · dailymed.usefulapi.io
claude mcp add --transport http io-usefulapi-dailymed 'https://dailymed.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-dailymed": {
"url": "https://dailymed.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-dailymed": {
"type": "http",
"url": "https://dailymed.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-dailymed] url = "https://dailymed.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-dailymed": {
"type": "remote",
"url": "https://dailymed.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-dailymed --url 'https://dailymed.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-dailymed:
url: "https://dailymed.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-dailymed": {
"Transport": "http",
"Url": "https://dailymed.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-dailymed -t streamable-http -u 'https://dailymed.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-dailymed": {
"type": "http",
"url": "https://dailymed.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +43
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 3 Oct 26 +15
- HTTPS: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://dailymed.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 dailymed.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://dailymed.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://dailymed.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://dailymed.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://dailymed.usefulapi.io/mcp |
| Authorisation server | https://dailymed.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dailymed.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://dailymed.usefulapi.io/mcp | HTTPS enforced | 301 | https://dailymed.usefulapi.io/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 →
dailymed_get_label Get full SPL label document (XML) ~128
Fetch the complete Structured Product Label for a SETID as HL7 v3 SPL XML — the full FDA-approved labeling: indications, dosage, warnings, boxed warning, adverse reactions, active/inactive ingredients, etc. NOTE: DailyMed serves the full document only as XML (there is no JSON form), so this returns raw XML text. Use dailymed_search_labels first to find the setid. DailyMed v2: GET /spls/{setid}.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| setid | string | yes | The label SETID (UUID) from dailymed_search_labels. |
No output schema declared.
No examples provided.
dailymed_label_history Get label version history ~107
List every published version (spl_version + published_date) of a label for a SETID — useful to see how a drug's labeling has changed over time. DailyMed v2: GET /spls/{setid}/history.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
| setid | string | yes | The label SETID (UUID). |
No output schema declared.
No examples provided.
dailymed_label_media Get label media (images) ~103
List media assets (product/packaging images, with mime_type and URL) for a label's current version, for a SETID. DailyMed v2: GET /spls/{setid}/media.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
| setid | string | yes | The label SETID (UUID). |
No output schema declared.
No examples provided.
dailymed_label_ndcs Get NDC codes for a label ~102
List the National Drug Codes (package-level NDCs) associated with a label's current version, for a SETID. DailyMed v2: GET /spls/{setid}/ndcs.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
| setid | string | yes | The label SETID (UUID). |
No output schema declared.
No examples provided.
dailymed_label_packaging Get label packaging & ingredients ~102
Get packaging descriptions plus product names and active ingredients (name + strength) for each product in a label, by SETID. DailyMed v2: GET /spls/{setid}/packaging.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
| setid | string | yes | The label SETID (UUID). |
No output schema declared.
No examples provided.
dailymed_list_application_numbers List FDA application numbers ~82
List FDA application numbers (NDA/ANDA/BLA) with their marketing category code, across all labels (paginated). DailyMed v2: GET /applicationnumbers.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
No output schema declared.
No examples provided.
dailymed_list_drug_classes List drug classes ~86
List pharmacologic drug classes linked to labels (code, coding system, type — e.g. EPC Established Pharmacologic Class — and name). DailyMed v2: GET /drugclasses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
No output schema declared.
No examples provided.
dailymed_list_drug_names List / search drug names ~138
List drug names in DailyMed (name + name_type B=brand/G=generic). Pass drug_name to filter by a substring — a fast way to discover exact spellings before searching labels. DailyMed v2: GET /drugnames.
| Name | Type | Req | Description |
|---|---|---|---|
| drug_name | string | – | Substring to filter drug names, e.g. 'aspirin'. |
| name_type | string | – | b=brand, g=generic, both. Default both. |
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
No output schema declared.
No examples provided.
dailymed_list_ndcs List all NDC codes ~77
List National Drug Codes across all labels in DailyMed (paginated; the full set is large). DailyMed v2: GET /ndcs.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
No output schema declared.
No examples provided.
dailymed_list_rxcuis List product-level RxCUIs ~88
List product-level RxNorm concept identifiers (rxcui + rxstring + rxtty term type) known to DailyMed (paginated). DailyMed v2: GET /rxcuis.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
No output schema declared.
No examples provided.
dailymed_list_uniis List UNII active moieties ~87
List FDA UNII codes and their active-moiety names (paginated). Use a unii_code to filter labels in dailymed_search_labels. DailyMed v2: GET /uniis.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
No output schema declared.
No examples provided.
dailymed_search_labels Search FDA drug labels (SPLs) ~343
Search Structured Product Labels (SPLs) — one label per marketed drug product. Filter by drug name, NDC, RxCUI, UNII, application (NDA/ANDA) number, marketing category, or publish date. Returns setid, title, spl_version and published_date for each match (use the setid with dailymed_get_label and the label_* tools). DailyMed v2: GET /spls.
| Name | Type | Req | Description |
|---|---|---|---|
| application_number | string | – | FDA application number, e.g. 'NDA020517'. |
| drug_name | string | – | Drug name to match (brand or generic), e.g. 'aspirin'. |
| marketing_category | string | – | Marketing category, e.g. 'NDA', 'ANDA', 'OTC MONOGRAPH DRUG'. |
| name_type | string | – | Restrict drug_name match: b=brand, g=generic, both. Default both. |
| ndc | string | – | National Drug Code, e.g. '46122-791-66'. |
| page | integer | – | Page number (1-based). Default 1. |
| pagesize | integer | – | Results per page (max 100). Default 100. |
| published_date | string | – | Publish date yyyy-MM-dd, paired with published_date_comparison. |
| published_date_comparison | string | – | Comparison operator for published_date. Default eq. |
| rxcui | string | – | RxNorm concept unique identifier (product-level). |
| setid | string | – | Filter to a specific SETID (UUID). |
| unii_code | string | – | FDA UNII code for an active moiety. |
No output schema declared.
No examples provided.
What is the io.usefulapi/dailymed MCP server?
io.usefulapi/dailymed is an MCP server listed in the public MCP registry as io.usefulapi/dailymed. Search DailyMed drug labels, SPLs, NDCs and packaging. This page covers its hosted endpoint (https://dailymed.usefulapi.io/mcp).
Is the io.usefulapi/dailymed MCP server safe to use?
io.usefulapi/dailymed scores 76 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 io.usefulapi/dailymed MCP server expose?
io.usefulapi/dailymed exposes 12 tools: dailymed_search_labels, dailymed_get_label, dailymed_label_history, dailymed_label_ndcs, dailymed_label_media, and 7 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.
Does the io.usefulapi/dailymed MCP server require authentication?
Yes. io.usefulapi/dailymed asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/dailymed MCP server still maintained?
io.usefulapi/dailymed is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.