Changelog
The service version is reported by serverInfo.version (MCP) and info.version (OpenAPI). Dates are Japan time. Before 1.0, a minor version can change field names; those changes are marked Changed.
0.9.1 — 2026-11-17
Section titled “0.9.1 — 2026-11-17”- Fixed: REST list parameters (such as
extra_holidays) can be repeated (a=1&a=2). Before, only the last value was used and the answer was silently wrong. Repeating any other parameter is now a400(invalid_input) instead of silently using the last value, and names such as__proto__are rejected as unknown, as they are over MCP. - Fixed:
normalize_addressmatches a town written with a leading 字 or 大字 (for example 与那国町字与那国); before, it matched only the city. The answer’snotessays that the prefix was left out. - Changed: 404 and 405 answers carry
type(not_found,method_not_allowed). The OpenAPIError.typelistsrate_limited,not_foundandmethod_not_allowedtoo.
0.9.0 — 2026-10-07
Section titled “0.9.0 — 2026-10-07”- Changed: the Japanese-era REST paths are now
/v1/japanese-era/to-era(Gregorian → era) and/v1/japanese-era/from-era(era → Gregorian). The era answer fields areinput_era,input_era_year(as given) andactual(the correct era date).0.8.0usedto-date/from-date. from_japanese_erareads a trailing weekday ((水) or 水曜日) and romaji era names (Reiwa 8.10.7). A mismatching weekday setsweekday_mismatch. Malformed kanji numerals and years above 200 are input errors.list_holidaysreturnstotal,returnedandtruncated(countis kept for now).- Operations: a build no longer deploys data older than what is live; the monthly refresh runs on the 3rd and the 10th; freshness limits (postal 60 days, corporate numbers 50 days) are shared by the deploy gate and the live check; downloads from the National Tax Agency have time limits.
0.8.0 — 2026-10-07
Section titled “0.8.0 — 2026-10-07”- Added:
to_japanese_eraandfrom_japanese_era. Era start dates: 大正 1912-07-30, 昭和 1926-12-25, 平成 1989-01-08, 令和 2019-05-01; supported from 1873-01-01. Dates outside an era are converted and markedoutside_era; future dates in the current era carryassumes_current_era.
0.7.0 — 2026-10-07
Section titled “0.7.0 — 2026-10-07”- Added: machine-readable
flagson every answer (estimated,unverified,truncated,not_found,closed,excluded_from_search,exact_match_only,partial,ambiguous,city_not_found,ambiguous_city). - Changed: lists use
total/returned/truncated(search_corporation_by_name:count→total); a closed corporation isis_closed(renamed fromclosedin name search, and added to number lookup);check_business_dayreturnsreason_code(weekend,holiday,bank_closure,extra_holiday);normalize_addressalways returnsaddress,municipality_codeandcity_candidates. - Errors now say whether the input was wrong (
Invalid input) or the server was (Server error); REST addstype. - A weekly live check also verifies data freshness.
0.6.1 — 2026-10-07
Section titled “0.6.1 — 2026-10-07”- The MCP
instructionsexplain which tool to use for what and how to show the corporate-number attribution.search_postal_codeexplains what to do when atownreturns nothing.
0.6.0 — 2026-10-07
Section titled “0.6.0 — 2026-10-07”- Added:
search_corporation_by_name(prefix search over the National Tax Agency data).
0.5.0 — 2026-10-07
Section titled “0.5.0 — 2026-10-07”- Added:
lookup_corporate_number(National Tax Agency full bulk data, PDL1.0 attribution).
0.4.0 — 2026-10-06
Section titled “0.4.0 — 2026-10-06”- Added:
normalize_address(to town level).
0.3.0 — 2026-10-06
Section titled “0.3.0 — 2026-10-06”- Postal lookups also cover Japan Post’s individual codes for large-volume business customers (
offices, and theoffice_namesearch).
0.2.0 — 2026-10-06
Section titled “0.2.0 — 2026-10-06”- Added:
lookup_postal_codeandsearch_postal_code. Deployment became automatic.
0.1.0 — 2026-10-06
Section titled “0.1.0 — 2026-10-06”- First version: the six calendar tools (
list_holidays,check_business_day,add_business_days,count_business_days,adjust_to_business_day,last_business_day_of_month) over MCP and REST.
Operated by Momonga