Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sfda Drugs

NPM · @PIPEWORX/MCP-SFDA-DRUGS · 2 COMPONENTS

SFDA Drugs — Saudi Food and Drug Authority drug data

+4 this week 83 Trust /100

Last scanned (10 hours ago)

Scores higher than 76% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sfda-drugs). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1205 tokens (~200/item across 6 items; 6 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 Management23
  • Stability observed for 7 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 5 Nov 26 +4
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Stability: unverified → 0.23 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-sfda-drugs@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-sfda-drugs
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-sfda-drugs/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3692347641
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ea3bbba48a44d9645d2c59eb05619465f266e6b3df6b0f5d1072b08df85edd43fcf5f2dede35f0166f28440e2dff69cf84772652e3069ea162a1fde80

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,148 tokens

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 →

Tool Tokens
sfda_clinical_trials ~229

Clinical trials registered with the SFDA and running in Saudi Arabia (sourced from www.sfda.gov.sa/en/drug_clinical_trials_list): study title, sponsor, status, study drug, phase, protocol number, and trial site (hospital). Filters are applied by the SFDA server.

NameTypeReqDescription
drugstring–Filter by study drug name substring, e.g. "VX 880".
pagenumber–Page number, zero-indexed (each page has 10-20 rows). Default 0.
phasestring–Filter by trial phase, e.g. "3".
protocol_numberstring–Filter by study protocol number.
sitestring–Filter by trial site (hospital/city) substring, e.g. "Riyadh".
sponsorstring–Filter by sponsor substring, e.g. "Pfizer".
statusstring–Filter by status substring, e.g. "Ongoing", "Terminated", "Completed".
titlestring–Filter by study title substring.

No output schema declared.

No examples provided.

sfda_drug_approvals ~163

Recent SFDA drug approvals in Saudi Arabia (sourced from www.sfda.gov.sa/en/new-sfda-drug-approvals): request type, drug type, trade name, scientific name, strength, dosage form, approval date. Newest first. Note: the SFDA leaves approval_date blank on the newest rows for a while — an empty date means SFDA has not published it yet, not a missing drug.

NameTypeReqDescription
pagenumber–Page number, zero-indexed (each page has 10-20 rows). Default 0.
scientific_namestring–Filter by scientific (generic) name substring, e.g. "semaglutide".
trade_namestring–Filter by trade name substring.

No output schema declared.

No examples provided.

sfda_drug_companies ~214

Drug companies and manufacturing sites registered with the SFDA (sourced from www.sfda.gov.sa/en/drug-companies): company name, address, registration status and number, certificate issue date (Hijri calendar), drug type, production line, and country. Filters are applied by the SFDA server. Arabic enum values are translated to English (originals kept in *_ar fields).

NameTypeReqDescription
countrystring–Filter by country name in Arabic as SFDA stores it (e.g. "فرنسا" for France). English values do not match.
namestring–Filter by company name (English) substring, e.g. "BAYER".
pagenumber–Page number, zero-indexed (each page has 10-20 rows). Default 0.
production_linestring–Filter by production line substring, e.g. "TABLET".
registration_nostring–Filter by company registration number, e.g. "1978/2".

No output schema declared.

No examples provided.

sfda_drug_details ~132

Full SFDA record for one entry from a list returned by sfda_drug_search or sfda_drug_shortages — registration number, trade/scientific name, price, and every other field the SFDA details page shows. Sourced from www.sfda.gov.sa details_data pages. Pass the nid and id from a row's details ref.

NameTypeReqDescription
idstringyesRow id from the details ref (numeric for drugs, a generic-name string for shortages).
nidstringyesList node id from the details ref (e.g. "17582" for the drugs list).

No output schema declared.

No examples provided.

sfda_drug_search ~236

Search Saudi Arabia registered human drugs with official SFDA prices in SAR. Scans the SFDA registered-drugs price list (sourced from www.sfda.gov.sa/en/drugs-list, ~14,000+ drugs across ~1,400 pages of 15-20 rows) and filters rows locally by scientific (generic) or trade name, because the SFDA site currently ignores its own search parameters. A single call scans a bounded window of pages, so to search the whole list keep calling with the returned next_page until done:true or you have enough matches. Omit query to simply browse pages in order. Each row carries a details ref for sfda_drug_details.

NameTypeReqDescription
pages_to_scannumber–How many consecutive pages to scan in this call (1-30). Default 10.
querystring–Case-insensitive substring matched against scientific name AND trade name (e.g. "metformin", "panadol"). Omit to list rows unfiltered.
start_pagenumber–Zero-indexed page of the SFDA list to start scanning from. Default 0.

No output schema declared.

No examples provided.

sfda_drug_shortages ~174

Current drug shortages in Saudi Arabia, sourced from the SFDA shortage list (www.sfda.gov.sa/en/currentlyInShortageList): generic name, availability status, and how many trade-name products are affected. Filters are applied by the SFDA server. Arabic status values are translated to English (original kept in status_ar).

NameTypeReqDescription
agent_namestring–Filter by local agent (distributor) name.
pagenumber–Page number, zero-indexed (each page has 10-20 rows). Default 0.
registration_nostring–Filter by SFDA registration number.
scientific_namestring–Filter by generic/scientific name substring, e.g. "AMOXICILLIN".
trade_namestring–Filter by trade name substring.

No output schema declared.

No examples provided.

Install

How do I install the Sfda Drugs MCP server?

Sfda Drugs runs locally as an npm package, launched with npx -y @pipeworx/mcp-sfda-drugs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-sfda-drugs

# add to Claude Code
claude mcp add pipeworx-io-sfda-drugs -- npx -y @pipeworx/mcp-sfda-drugs
Common questions

What is the Sfda Drugs MCP server?

Sfda Drugs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sfda-drugs. SFDA Drugs, Saudi Food and Drug Authority drug data. This page covers its npm package (@pipeworx/mcp-sfda-drugs).

Is the Sfda Drugs MCP server safe to use?

Sfda Drugs scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Sfda Drugs MCP server expose?

Sfda Drugs exposes 6 tools: sfda_drug_search, sfda_drug_details, sfda_drug_shortages, sfda_drug_approvals, sfda_clinical_trials, sfda_drug_companies. Their descriptions and schemas cost roughly 1,148 tokens of context every time the server is loaded.

Is the Sfda Drugs MCP server still maintained?

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

What licence is the Sfda Drugs MCP server under?

Sfda Drugs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.