Skip to content

Trust & transparency

This page says where the data comes from, how fresh it is, how it is checked, what the answers cannot tell you, and what we have and have not verified. Where we could not confirm something, it says so.

Data Source Terms and attribution Version in each answer
Corporate numbers National Tax Agency (国税庁), Corporate Number Publication Site, “basic 3 items” full bulk data (CSV, Unicode) Public Data License 1.0 (PDL1.0). Answers carry source.attribution (“…を加工して作成” — created by processing the source data). Please keep it when you show the data. source.data_version
Postal codes and addresses Japan Post (日本郵便) postal code data (address data, and the individual codes for large-volume business customers) Japan Post states that it does not claim copyright over the postal code data; the exact wording is returned in source.license source.data_updated
Holidays and business days Calculated from the National Holidays Act (国民の祝日に関する法律), then compared with the Cabinet Office (内閣府) “National Holidays” CSV Cabinet Office data: attribution under the Government Standard Terms of Use source.verification
Japanese eras Calculated from the era start dates — —
  • Corporate-number and postal data are rebuilt and deployed automatically on the 3rd and 10th of each month. The second run exists because the new files are sometimes not yet published on the 3rd. Code changes redeploy the same data.
  • Deploy gates. A build is stopped, and production keeps serving the previous data, if the row counts fall below fixed floors, if files are missing, if the name index is inconsistent with the corporate-number data, or if the data is older than what is already live.
  • Freshness limits. Postal data must be no more than 60 days old and corporate-number data no more than 50 days old. A scheduled live check fails when data is older than that.
  • Current versions (read on 2026-11-17): corporate numbers 2026-10-30, postal codes 2026-10-30, both 18 days old. Always read source in the answer you receive; this page can be out of date.
  • Not real time. Corporate-number data is a monthly snapshot. A corporation registered or changed after the snapshot is not reflected, and not_found does not prove that a corporation does not exist.
  • Holidays. Computed from the law and compared with the Cabinet Office CSV. The answer’s source.verification states what was compared (read on 2026-11-17: 1980–2027, dates and names matching, confirmed 2026-10-06, compared weekly since). A weekly comparison is configured.
  • Corporate numbers. The check digit of every row is validated when the data is built; the build fails on any mismatch.
  • After every deploy a smoke test calls every tool and endpoint of the live service.
  • Years after 2027 have not been compared with Cabinet Office data. Their answers carry unverified. Future spring and autumn equinox days are calculated by formula, because the official date is announced in the government gazette in February of the previous year; they carry estimated.
  • A future date written as a Japanese-era date assumes the era does not change (assumes_current_era).
  • When one of these flags is present, tell the end user instead of presenting the value as certain.
  • Addresses are matched to the town level (町域) only. The service does not confirm that a block or building number exists, and returns no latitude or longitude.
  • Corporate numbers are not an invoice registration check. Corporations marked “excluded from search” in the source data are returned by number (with excluded_from_search) but not by name search.
  • Name search is a prefix match on the corporate name (legal-form words such as 株式会社 are ignored) and returns at most 100 results.
  • Japanese-era conversion starts at 1873-01-01. Holidays cover 1980–2099.
  • Company-specific closed days must be supplied by the caller (extra_holidays).
  • No batch requests, no streaming, no authentication, no per-customer quota, and no uptime guarantee.

As of 2026-11-17 we know of no incorrect answers that are confirmed and still unfixed. Corrections are listed in the changelog; version 0.9.1 fixed repeated REST parameters, addresses written with 字 / 大字, and the error type values. Protocol limits (no batching, no streaming) are listed under known limitations above.

Run on 2026-11-17 against the public endpoint (service version 0.9.1), read-only and at low volume.

Check Tool and version Result
Connect, tools/list, tools/call MCP Inspector CLI 2.15.0 (Streamable HTTP) 13 tools listed; a to_japanese_era call returned without error
Server conformance: server-initialize, ping, tools-list @modelcontextprotocol/conformance 0.1.16 3 of 3 passed
Server conformance: all other scenarios the same Not run. They test features this server does not offer (resources, prompts, logging, completion, sampling, elicitation, SSE streams) or require fixed test tools
Own smoke test: protocol versions 2025-06-18 / 2025-03-26 / 2024-11-05, 13 tools with read-only annotations, error shapes, CORS, 13 REST endpoints, OpenAPI consistency, data freshness scripted, 40 checks 40 of 40 passed

Not covered: authentication (there is none), streaming (not used), load behaviour and availability over time (not tested; there is no SLA).

These are the results of the checks above, not a certification.

MCP directories publish scores for servers. Such scores reflect each directory’s own method, change over time, and are not security certifications.

We do not show a directory score on this site, because we could not confirm a current, dated score and its method. If we add one, it will state the directory, the date it was read and a link to the listing.

Operated by Momonga. Contact details are not published at this time.

See the changelog.

Operated by Momonga