# Aemps Cima (npm · @pipeworx/mcp-aemps-cima)

AEMPS CIMA — the Spanish Agency for Medicines and Health Products' public register of every…

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 79/100, [markdown](https://verifymcp.io/servers/pipeworx-io-aemps-cima/aemps-cima-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-aemps-cima/aemps-cima-mcp)
- npm · `@pipeworx/mcp-aemps-cima`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-aemps-cima/pipeworx-mcp-aemps-cima.md), [page](https://verifymcp.io/servers/pipeworx-io-aemps-cima/pipeworx-mcp-aemps-cima)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-aemps-cima`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-aemps-cima).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-aemps-cima -- npx -y @pipeworx/mcp-aemps-cima
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-aemps-cima": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-aemps-cima"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-aemps-cima": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-aemps-cima"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-aemps-cima -- npx -y @pipeworx/mcp-aemps-cima
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-aemps-cima": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-aemps-cima"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-aemps-cima --command npx --arg -y --arg @pipeworx/mcp-aemps-cima
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-aemps-cima:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-aemps-cima"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-aemps-cima": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-aemps-cima"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-aemps-cima -t stdio -c npx -a -y @pipeworx/mcp-aemps-cima
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-aemps-cima": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-aemps-cima"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +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.

### 2026-11-03 (score 82, +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.

### 2026-11-01 (score 81, +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.

### 2026-10-30 (score 80, +1)

- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (5)

### `cima_search_medicines` (~337 tokens)

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.

Input parameters:

- `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"

### `cima_medicine_detail` (~141 tokens)

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.

Input parameters:

- `nregistro` (string, required): Spanish national registration number, e.g. "77758"

### `cima_medicine_document_sections` (~294 tokens)

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.

Input parameters:

- `document` (string): ficha_tecnica = SmPC (prescriber label); prospecto = patient leaflet. Default ficha_tecnica.
- `nregistro` (string, required): Spanish national registration number, e.g. "77758"
- `seccion` (string): One section number to fetch alone, e.g. "4.1" (indications). Omit for every section.

### `cima_supply_problems` (~194 tokens)

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.

Input parameters:

- `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.

### `cima_changes_since` (~160 tokens)

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.

Input parameters:

- `limit` (number): Max rows to return (default 50, max 200)
- `since` (string, required): ISO date, e.g. "2026-08-27" — returns changes on or after this date.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-aemps-cima/pipeworx-mcp-aemps-cima#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79

## Common questions

### 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.

### What did VerifyMCP test on the Aemps Cima MCP server?

VerifyMCP ran 16 checks on Aemps Cima, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-aemps-cima
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-aemps-cima
- Repository: https://github.com/pipeworx-io/mcp-aemps-cima
- Website: https://pipeworx.io/packs/aemps-cima
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-aemps-cima/pipeworx-mcp-aemps-cima.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-aemps-cima/pipeworx-mcp-aemps-cima/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-aemps-cima/pipeworx-mcp-aemps-cima.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-aemps-cima/pipeworx-mcp-aemps-cima