Swissmedic
NPM · @PIPEWORX/MCP-SWISSMEDIC · 2 COMPONENTS
Swissmedic authorised human medicines — the 'Zugelassene Arzneimittel HAM' list, Switzerland's…
Available components
Last scanned (7 hours ago)
Scores higher than 80% 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-swissmedic). 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 Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 559 tokens (~139/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 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 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +2
- Stability: unverified → 0.17 ▲ functional
- 29 Oct 26 81
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-swissmedic@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-swissmedic |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-swissmedic/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3701223788 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:50910b992450c29869b1f2c16a282cffb72e4aa5ccf6191306917670f8441a72993a5f4e4948c64f2fd71577f5eb5afd89e31f1adf3de9040b41cf3e7 |
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 →
swissmedic_dataset_info ~48
Dataset metadata: the authoritative Swissmedic bulk-download URL, the source page, current row count, and the full list of distinct medicine categories and dispensing categories used by the search filters.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
swissmedic_product ~105
The full Swissmedic record(s) for one product by name — every authorised dosage strength, its own authorisation number and dates. Swissmedic's export carries no indication text and no per-product URL, so this returns the authoritative Swissmedic download instead of a paraphrased indication.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Exact or near-exact product name, e.g. "Vivotif, Kapseln", as it appears in the Swissmedic export. |
No output schema declared.
No examples provided.
swissmedic_recent_changes ~77
Products first authorised, or with a dosage strength newly authorised, in Switzerland since a given date — a real change signal from the source's own date columns (unlike EMA's Article 57 register, this file does carry authorisation dates).
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | yes | Earliest authorisation date to include, YYYY-MM-DD. |
No output schema declared.
No examples provided.
swissmedic_search ~274
Search Swissmedic's authorised human medicines register (Switzerland) — every authorised product and each of its authorised dosage strengths, with the marketing-authorisation holder, medicine category, dispensing category (prescription tier) and authorisation dates. Answers "is <product> authorised in Switzerland", "who holds the Swiss authorisation for <product>", "what dispensing category is <product> in Switzerland". Real offset+limit pagination with a total match count.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter on Swissmedic medicine category ("Heilmittelcode"), e.g. "Impfstoffe" (vaccines), "Blutprodukte" (blood products) — substring match. |
| dispensing_category | string | – | Filter on dispensing category, e.g. "A" (single dispensing, doctor/pharmacist), "B" (prescription-only), "C"/"D"/"E" (pharmacy/drugstore/general sale). Matches either the dosage-level or medicine-lev… |
| holder | string | – | Filter on marketing authorisation holder (substring match). |
| limit | number | – | Max rows to return, default 25, max 200. |
| offset | number | – | Row offset for pagination, default 0. |
| query | string | – | Free text: product name or marketing-authorisation holder. |
No output schema declared.
No examples provided.
How do I install the Swissmedic MCP server?
Swissmedic runs locally as an npm package, launched with npx -y @pipeworx/mcp-swissmedic. 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-swissmedic
claude mcp add pipeworx-io-swissmedic -- npx -y @pipeworx/mcp-swissmedic
What is the Swissmedic MCP server?
Swissmedic is an MCP server listed in the public MCP registry as io.github.pipeworx-io/swissmedic. Swissmedic authorised human medicines, the 'Zugelassene Arzneimittel HAM' list, Switzerland's… This page covers its npm package (@pipeworx/mcp-swissmedic).
Is the Swissmedic MCP server safe to use?
Swissmedic scores 84 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 Swissmedic MCP server expose?
Swissmedic exposes 4 tools: swissmedic_search, swissmedic_product, swissmedic_recent_changes, swissmedic_dataset_info. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.
Is the Swissmedic MCP server still maintained?
Swissmedic 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 Swissmedic MCP server under?
Swissmedic declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Swissmedic MCP server?
VerifyMCP ran 16 checks on Swissmedic, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.