Japan Regional Influenza Records

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

How much influenza is this Japanese prefecture reporting this week? Hosted, recorded daily.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Lets an assistant look up weekly influenza case records for Japanese prefectures from a hosted, daily-updated source.

What you can do
This remote MCP server provides access to recorded influenza surveillance data for Japanese prefectures. According to the registry description, it answers questions such as how much influenza a given prefecture is reporting in a given week, with the data hosted and recorded daily. No individual tools are listed in the manifest, so the exact query interface is not documented here.
When to use it
Useful when an assistant needs current or recent influenza activity figures for Japan broken down by prefecture, for example for public-health questions, regional comparisons, or situational summaries.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, account, API key, or environment variable is declared. Network access to the hosted endpoint is required.
Before you install
The manifest declares no authentication, so treat queries as non-private. The data is third-party surveillance reporting; verify figures against official sources before relying on them for health or policy decisions.

Installation

In SourceWeft

  1. Open Japan Regional Influenza Records 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-flu-regional/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-regional-influenza-records": {
      "type": "http",
      "url": "https://jp-flu-regional-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.

flu_region_snapshot

Influenza snapshot for a Japanese region

What is the latest weekly flu count per sentinel for Japan, a prefecture or a covered health-center area? ISO week, value, recent weeks, official warning/advisory where announced (status_basis official), separate from a comparison with reference values (status_basis computed), school-closure counts by facility type and action where covered (no school names), tracking_since and receipts (url, fetched_at, sha256). Optional as_of date. Descriptive statistics only, no medical or travel advice.

Parametersas_ofprefecturerequiredhealth_center

flu_region_history

Recorded influenza changes for a region

What changed in the recorded influenza figures for a Japanese region since a date? Versions this service recorded: new weeks (first_recorded) and revised values (revised, with the old value) of weekly per-sentinel figures, official statuses and school-closure counts, with observed_at, source URL and raw-file sha256, plus tracking_since and fetch gaps. From our own daily records; values the publisher later overwrote stay visible. Free: last 30 days of records. Descriptive statistics only.

Parameterslimitsincerequireddatasetprefecturerequiredhealth_center

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.