Hsa Singapore
NPM · @PIPEWORX/MCP-HSA-SINGAPORE · 2 COMPONENTS
Singapore HSA registered therapeutic products — the Health Sciences Authority's official 'Listing…
Available components
Last scanned (12 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
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-hsa-singapore). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 872 tokens (~218/item across 4 items; 4 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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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 +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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-hsa-singapore@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-hsa-singapore |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-hsa-singapore/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637394110 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ac0fb72db219d887518ec94e4e10007cf40374a971756dc94f9f1baadb7d52ffccaecce632a50eb9ba72623726e3d43c74990e34359a5730ca26cce82 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
hsa_sg_dataset_info ~84
Metadata for the Singapore HSA registered therapeutic products listing: row count, source last-updated date, latest approval date present, the bulk-download page, licence, fields present and absent, and the distinct values (with counts) for forensic classification, country of manufacture, route and dosage form — use it for exact filter spellings before hsa_sg_search.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hsa_sg_product ~153
The full HSA registration record for one Singapore therapeutic product, by SIN licence number (exact) or product name (exact, else substring with match_type marked): licence holder, approval date, forensic classification, ATC code, dosage form, route, manufacturers, active ingredients with strengths. The listing carries no indication text, so this returns the authoritative HSA listing and infosearch URLs rather than a paraphrased indication.
| Name | Type | Req | Description |
|---|---|---|---|
| licence_no | string | – | SIN licence number, e.g. "SIN06670P". |
| name | string | – | Product name as registered, e.g. "DOUBLE PARROT BRAND ADULT FEVER TABLETS 500 mg". Used when licence_no is not given. |
No output schema declared.
No examples provided.
hsa_sg_recent_changes ~131
Therapeutic products newly registered in Singapore by HSA on or after a date, from each product's approval date, newest first. Covers NEW REGISTRATIONS only: the listing holds only currently registered products and no cancellation or variation date, so withdrawals are invisible and the response says so (removals_visible:false). Returns comparable:false with a reason, never a misleading zero, when the date is later than the published data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows, default 50, max 500. |
| since | string | yes | Earliest approval date to include, YYYY-MM-DD. |
No output schema declared.
No examples provided.
hsa_sg_search ~448
Search medicines registered in Singapore — the Health Sciences Authority (HSA) official listing of ~5,500 registered therapeutic products, live from data.gov.sg. Answers "is <drug> approved in Singapore", "which Singapore-registered products contain <ingredient>", "what does <company> hold a Singapore product licence for", "which products in ATC class <code> are registered in Singapore". Each row: SIN licence number, product name, licence holder, approval date, forensic classification (Prescription Only / Pharmacy Only / General Sale List), ATC code, dosage form, route, manufacturers, country of manufacture, active ingredients with strengths. Real offset+limit pagination with a total match count; results newest approval first.
| Name | Type | Req | Description |
|---|---|---|---|
| active_ingredient | string | – | Active ingredient contains (case-insensitive), e.g. "PARACETAMOL". |
| approved_from | string | – | Earliest approval date, YYYY-MM-DD. |
| approved_to | string | – | Latest approval date, YYYY-MM-DD. |
| atc_code | string | – | ATC code prefix, e.g. "A10BA" (biguanides) or "L01" (antineoplastics). |
| country | string | – | Country of manufacture, exact name as HSA writes it, e.g. "INDIA", "GERMANY" (see hsa_sg_dataset_info). |
| dosage_form | string | – | Dosage form contains, e.g. "TABLET", "INJECTION". |
| forensic_classification | string | – | Supply category. |
| holder | string | – | Product licence holder name contains, e.g. "PFIZER". |
| limit | number | – | Max rows, default 25, max 200. |
| manufacturer | string | – | Manufacturer name contains. |
| offset | number | – | Row offset for pagination, default 0. |
| query | string | – | Free text matched against product name, active ingredient, licence holder and licence number, e.g. "metformin", "KEYTRUDA", "SIN16061P". |
| route | string | – | Route of administration contains, e.g. "ORAL", "INTRAVENOUS". |
No output schema declared.
No examples provided.
How do I install the Hsa Singapore MCP server?
Hsa Singapore runs locally as an npm package, launched with npx -y @pipeworx/mcp-hsa-singapore. 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-hsa-singapore
claude mcp add pipeworx-io-hsa-singapore -- npx -y @pipeworx/mcp-hsa-singapore
What is the Hsa Singapore MCP server?
Hsa Singapore is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hsa-singapore. Singapore HSA registered therapeutic products, the Health Sciences Authority's official 'Listing… This page covers its npm package (@pipeworx/mcp-hsa-singapore).
Is the Hsa Singapore MCP server safe to use?
Hsa Singapore scores 82 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 Hsa Singapore MCP server expose?
Hsa Singapore exposes 4 tools: hsa_sg_search, hsa_sg_product, hsa_sg_recent_changes, hsa_sg_dataset_info. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.
Is the Hsa Singapore MCP server still maintained?
Hsa Singapore 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 Hsa Singapore MCP server under?
Hsa Singapore declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.