Japan Regional Influenza Records MCP Server

by mk-career-planning Your server? Claim it

answering

Japan Regional Influenza Records is answering right now. Last checked 5 min ago. It exposes 4 tools.

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

Uptime history 14 days of history

14 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1206 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Japan Regional Influenza Records every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add jp-flu-regional --transport http https://jp-flu-regional-production.mk-career-planning.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://jp-flu-regional-production.mk-career-planning.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.jp-flu-regional]
url = "https://jp-flu-regional-production.mk-career-planning.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "jp-flu-regional": {
      "url": "https://jp-flu-regional-production.mk-career-planning.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "jp-flu-regional": {
      "type": "http",
      "url": "https://jp-flu-regional-production.mk-career-planning.workers.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

flu

flu_region_history

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.

flu_region_snapshot

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.

catalog

catalog

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

receipt

get_receipt

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.

Endpoints

URL	Transport	State	Latency	Checked
https://jp-flu-regional-production.mk-career-planning.workers.dev/mcp	streamable-http	answering	927 ms	5 min ago

Alternatives to Japan Regional Influenza Records

same job, measured the same way

Search that shows its work

by ag-bureau

Self-hosted web search that reports how much of each answer to believe

local only

TokenKnows

by johnnywuj81

Distill AI coding sessions into weekly reports, ADRs and a knowledge graph - self-hosted

124 installs/wk local only

COMPAMIR News

by compamir

Search structured COMPAMIR news in Japanese and English, with links to source reports.

3 tools answering

Pulse

by allthepossibles

Core Web Vitals (LCP, INP, CLS) per URL from the Chrome UX Report, with daily checks on Pro.

1 tools answering

DashThis

by dashthis

Work with your marketing reporting dashboards and turn the numbers into client-ready updates.

answering

WhichPost (public)

by whichpost

What WhichPost is, how it works, pricing and a simulated sample report. No sign-in.

7 tools answering

PageSpeed Insights MCP

by considus

One run is noise, so this reports the median of several distinct PageSpeed analyses and the spread.

local only

Issuecapture

by issuecapture

Install the IssueCapture bug reporting widget for Jira. Auto-detects your framework.

10 installs/wk local only

Japan Regional Influenza Records — questions

Answers built from our own checks of this server.

What can Japan Regional Influenza Records do?

It exposes 4 tools, read directly from the server on our last check. Among them: catalog, flu_region_history, flu_region_snapshot, get_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Japan Regional Influenza Records working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1206 ms. The bar chart above shows every period we have measured.

How do I connect Japan Regional Influenza Records?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Japan Regional Influenza Records need an API key?

No. Japan Regional Influenza Records completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Japan Regional Influenza Records?

It answers our handshake in 1206 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.