Japan Drug Supply Status Relay

io.github.mk-career-planningPublished by GitHub account mk-career-planningv0.1.0Updated Oct 24, 2026

Is this drug's shipment normal, limited or suspended in Japan (MHLW)? Hosted, history kept.

The publisher's own server: status.live national parks

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant check whether a drug's shipment in Japan is normal, limited, or suspended, based on MHLW supply information.

What you can do
A hosted remote MCP server that answers questions about the shipment status of drugs in Japan, reporting whether supply is normal, limited, or suspended according to MHLW (Japan's Ministry of Health, Labour and Welfare). It keeps a history of the status information it serves. No tool list is published in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs to answer questions about Japanese drug availability or supply restrictions, for example for pharmacy, clinical, or procurement research. It is a read-only lookup service, so it fits fact-checking and monitoring rather than any workflow that changes data.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, account, API key, or environment variable is declared. The assistant or client must be able to reach the hosted endpoint over the network.
Before you install
The server is third-party hosted and no authentication is declared, so queries are not tied to a verified identity and the operator can see request traffic. Supply-status data is reference information from a government source and should be confirmed against official MHLW publications before it is relied on for clinical or procurement decisions.

Installation

In SourceWeft

  1. Open Japan Drug Supply Status Relay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mk-career-planning%2Fjp-drug-supply/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "japan-drug-supply-status-relay": {
      "type": "http",
      "url": "https://jp-drug-supply-production.mk-career-planning.workers.dev/mcp"
    }
  }
}

Tools

4

catalog

Catalog: tools, prices and limits

List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

Takes no parameters.

drug_supply_status

Drug shipment status in Japan (MHLW list)

What shipment status has MHLW published for this prescription drug in Japan? Look up by YJ code, NHI price list code, or Japanese product or ingredient name. Returns the shipment status as published by MHLW (normal, limited shipment and its sub-category, supply suspended) with English labels as our translation, reason, outlook, manufacturer, MHLW dates and the previous status observed by this service. Relay only: not medical advice, not a statement about any pharmacy's stock.

Parametersqueryrequiredmax_results

drug_supply_changes

Drug shipment status changes since a date

Which products in the Japan MHLW supply status list changed status, or were added, removed or modified, since a date? From this service's own record of list versions (MHLW publishes only the current list). Each change has the YJ code, product, status before and after (as published, with English labels as our translation) and the versions compared. History starts at tracking_since; nothing earlier was observed. Free: last 30 days (see history_window). Relay only.

Parameterslimitsincerequiredyj_codechange_type

get_receipt

Get receipt of a paid call

Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.

Parametersreceipt_idrequired

Version history

1
  1. v0.1.0LatestOct 12, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Status integrations