Skip to main content
Glama
aifa-medicines

aifa-medicines

by pipeworx-io
README.md
# @pipeworx/aifa-medicines

AIFA, the Italian Medicines Agency's register of authorised medicines: search by brand name or active ingredient, and get the full record for one product in **Italy** (holder, status, ATC code, packs with AIC numbers, leaflet and SmPC links).

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1957+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Scope: Italy only

For the US use `openfda`; EU-wide, `ema-medicines`; UK, `mhra-uk`; Australia, `tga-artg`; Spain, `aemps-cima`. Tools are prefixed `aifa_` so they never win a generic drug question.

## Tools

- `aifa_drug_search(query, limit?, page?)` — *Which Italian products contain ibuprofene? What is Tachipirina?* Returns brand name, active ingredients, form, route, authorisation holder, status, ATC code and packs. 10 per page, `page` is 0-based; the response carries `total`, `has_more` and `next_page`. Zero matches returns `found: false` with an `empty_reason`.
- `aifa_drug_get(id)` — the full record for one AIFA product id, with every pack (AIC number, authorisation date, supply and reimbursement class) and leaflet / SmPC PDF links where published. Unknown id returns `found: false`.

Every response carries `source` and `data_as_of` (fetch time: the register is queried live per request and nothing is stored).

## Auth

Keyless.

## Data sources

- AIFA (Agenzia Italiana del Farmaco), Banca Dati Farmaci: the register of medicines authorised in Italy.

### Things the next person would otherwise rediscover

- **Matching is Italian-first and fuzzy.** "ibuprofene" returns 247 entries, "ibuprofen" only 3. Use the Italian ingredient or brand; the empty-result message says so.
- **The unit is a product in one strength and form**, not a brand. "Tachipirina" returns 21 entries (one per strength/form), each with its own packs.
- **Page size is fixed at 10** upstream; `limit` can only trim a page.
- **An empty query is refused** upstream (HTTP 400), so the pack refuses it first with a clear message.
- **Status** is the register's own value (`AUTORIZZATA` per pack, product-level `authorised`); revoked and suspended are separate flags, never inferred.
- Italian-language text only; the register has no English names for brands.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "aifa-medicines": {
      "url": "https://gateway.pipeworx.io/aifa-medicines/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/aifa-medicines/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1957+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## No MCP client? Call it over HTTP

```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/aifa_drug_search \
  -H 'Content-Type: application/json' \
  -d '{"query":"tachipirina"}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/aifa_drug_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-aifa-medicines` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/aifa-medicines/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "aifa-medicines": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-aifa-medicines"]
    }
  }
}
```

Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.

It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Aifa Medicines data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT