Skip to main content
Glama
jp-nhi-drug-prices

jp-nhi-drug-prices

by pipeworx-io
README.md
# @pipeworx/jp-nhi-drug-prices

Japan's official National Health Insurance (NHI) drug prices as the Ministry of Health, Labour and Welfare (厚生労働省) publishes them: the list of drugs covered by insurance, with the price in yen per unit, whether each product is an originator or a generic, and the date the current edition applies from.

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

## Tools

- `jp_nhi_drug_price(query, category?, limit?)` — looks up drugs in the ministry's list of insured drugs (薬価基準収載品目リスト). Each row has the brand name, active ingredient, specification and unit (the price is per that unit), manufacturer, NHI price in yen, product type (originator 先発品, quasi-originator 準先発品 or generic 後発品), whether a generic is eligible for add-on payment, the 12-character drug price list code, listing and transitional-period notes, and marks such as Japanese Pharmacopoeia or narcotic. `category` is `oral` (内用薬), `injection` (注射薬), `external` (外用薬), `dental` (歯科用薬剤) or `all` (default); only the categories asked for are read. The list is Japanese and carries no Latin ingredient names: search with katakana or kanji brand, ingredient or manufacturer words (full/half width and hiragana/katakana are folded) or the 12-character code. Every answer states the edition of the list and its applies-from date; a zero-match answer says which categories were searched.

## Auth

Keyless.

## Data sources

- Ministry of Health, Labour and Welfare (厚生労働省), NHI drug price standard, list of drugs covered by health insurance (薬価基準収載品目リスト): read live per call, nothing stored; an isolate keeps a parsed copy for six hours. The ministry re-issues the list with each price revision and new listing, so `applies_from` and `data_as_of` give the date of the edition read.

Traps worth knowing: prices are official reimbursement prices per unit of the specification (per tablet, per mL, per vial), not retail or purchase prices; the list has no English names, so an English ingredient query finds nothing and the answer says so; the ministry's separate list of generic-drug equivalents and its notes on listing are not read; medical devices and non-listed drugs are not in the list.

## Quick Start

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

```json
{
  "mcpServers": {
    "jp-nhi-drug-prices": {
      "url": "https://gateway.pipeworx.io/jp-nhi-drug-prices/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/jp-nhi-drug-prices/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 2016+ 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/jp_nhi_drug_price \
  -H 'Content-Type: application/json' \
  -d '{"query":"キイトルーダ","category":"injection","limit":3}'
```

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

## Run it from npm

`@pipeworx/mcp-jp-nhi-drug-prices` 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/jp-nhi-drug-prices/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "jp-nhi-drug-prices": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-jp-nhi-drug-prices"]
    }
  }
}
```

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 Jp Nhi Drug Prices 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