Aemps Cima
NPM · @PIPEWORX/MCP-AEMPS-CIMA · 2 COMPONENTS
AEMPS CIMA — the Spanish Agency for Medicines and Health Products' public register of every…
Available components
Last scanned (3 hours ago)
Scores higher than 76% 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-aemps-cima). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1182 tokens (~236/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Package version: 0.2.0 → 0.2.1 functional
- 29 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-aemps-cima@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-aemps-cima |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-aemps-cima/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3587857353 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:29de79fc41019601bb4601de111884215ae0307d3e2f3add8804044690e361f58b13da12e42a572adf84d91f50abc0e320630530757b1db24aad28151 |
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 →
cima_changes_since ~160
Which Spanish medicine records AEMPS has changed on or after a given date — new authorisations, label revisions, material-informativo updates, etc. — from CIMA's registroCambios feed. Returns nregistro, name, holder, the change date, and AEMPS's change-category tags. Useful for "what changed in the Spanish medicines register this month" or watching one drug for label updates. Example: cima_changes_since({ since: "2026-08-27" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows to return (default 50, max 200) |
| since | string | yes | ISO date, e.g. "2026-08-27" — returns changes on or after this date. |
No output schema declared.
No examples provided.
cima_medicine_detail ~141
Full AEMPS CIMA record for one Spanish-authorised medicine, by nregistro (the Spanish national registration number, from cima_search_medicines). Returns active ingredients with exact strength, excipients, ATC codes, pharmaceutical form, routes of administration, prescription status, authorisation and last-revision dates, and PDF/HTML links to the ficha técnica and prospecto. For the actual document TEXT (not just the link) use cima_medicine_document_sections. Example: cima_medicine_detail({ nregistro: "77758" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| nregistro | string | yes | Spanish national registration number, e.g. "77758" |
No output schema declared.
No examples provided.
cima_medicine_document_sections ~294
The STRUCTURED text of a Spanish medicine's ficha técnica (Summary of Product Characteristics) or prospecto (patient information leaflet), section by section, from AEMPS's own segmented-document endpoint — not a PDF link. Ficha técnica sections cover indications (4.1), dosage (4.2), contraindications (4.3), warnings (4.4), interactions (4.5), pregnancy/lactation (4.6), adverse effects (4.8), overdose (4.9). Pass seccion (e.g. "4.1") to fetch one section only; omit it to get every section (each capped at ~4000 chars to keep the payload bounded — the response says which sections were truncated). Example: cima_medicine_document_sections({ nregistro: "77758", document: "ficha_tecnica", seccion: "4.1" }); cima_medicine_document_sections({ nregistro: "77758", document: "prospecto" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | – | ficha_tecnica = SmPC (prescriber label); prospecto = patient leaflet. Default ficha_tecnica. |
| nregistro | string | yes | Spanish national registration number, e.g. "77758" |
| seccion | string | – | One section number to fetch alone, e.g. "4.1" (indications). Omit for every section. |
No output schema declared.
No examples provided.
cima_search_medicines ~337
Search AEMPS CIMA — the register of every medicine authorised for sale in SPAIN — by brand/product name, active ingredient (INN/DCI), ATC code, or marketing-authorisation holder (laboratorio). Returns each medicine's nregistro (Spanish national registration number), the active substance, dosage, prescription status, marketed/generic/orphan/biosimilar flags, and links to its ficha técnica (SmPC) and prospecto (patient leaflet). Field values and matching are SPANISH: search "paracetamol" or "ibuprofeno", not a US brand name. Answers "is X authorised in Spain", "which Spanish medicines contain ibuprofeno", "Spanish generics of atorvastatin". Example: cima_search_medicines({ ingredient: "paracetamol" }); cima_search_medicines({ name: "Nolotil" }); cima_search_medicines({ atc: "N02BE01" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| atc | string | – | ATC code, e.g. "N02BE01" |
| ingredient | string | – | Active ingredient (INN/DCI, Spanish form), e.g. "paracetamol", "ibuprofeno", "amoxicilina" |
| lab | string | – | Marketing-authorisation holder (laboratorio titular), e.g. "Cinfa" |
| limit | number | – | Max medicines to return (default 25, max 200) |
| name | string | – | Brand/product name, Spanish spelling, e.g. "Nolotil", "Paracetamol Cinfa" |
No output schema declared.
No examples provided.
cima_supply_problems ~194
Current and recent medicine-supply shortages in Spain (problemas de suministro) from AEMPS — the Spanish counterpart of the FDA/EMA shortage databases. Returns the affected product, national code (CN), AEMPS shortage-type code, start date, expected end date (open-ended if none), whether it is still active, and AEMPS's own observation text (often naming an alternative). Only the product name filters this endpoint upstream (not the lab). Answers "is there a shortage of X in Spain", "current Spanish drug supply problems". Example: cima_supply_problems({}); cima_supply_problems({ name: "eltrombopag" }). Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows to return (default 50, max 200) |
| name | string | – | Medicine name to filter by, e.g. "eltrombopag". Omit for all current supply problems. |
No output schema declared.
No examples provided.
How do I install the Aemps Cima MCP server?
Aemps Cima runs locally as an npm package, launched with npx -y @pipeworx/mcp-aemps-cima. 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-aemps-cima
claude mcp add pipeworx-io-aemps-cima -- npx -y @pipeworx/mcp-aemps-cima
What is the Aemps Cima MCP server?
Aemps Cima is an MCP server listed in the public MCP registry as io.github.pipeworx-io/aemps-cima. AEMPS CIMA, the Spanish Agency for Medicines and Health Products' public register of every… This page covers its npm package (@pipeworx/mcp-aemps-cima).
Is the Aemps Cima MCP server safe to use?
Aemps Cima 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 Aemps Cima MCP server expose?
Aemps Cima exposes 5 tools: cima_search_medicines, cima_medicine_detail, cima_medicine_document_sections, cima_supply_problems, cima_changes_since. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.
Is the Aemps Cima MCP server still maintained?
Aemps Cima 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 Aemps Cima MCP server under?
Aemps Cima declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.