Gbizinfo MCP server

@pipeworx/gbizinfo

Japanese corporate registry — company profiles, government procurement awards, subsidies, patents, certifications, financials and workplace disclosure, keyed on the 13-digit 法人番号 (corporate number). Source: gBizINFO, Ministry of Economy, Trade and Industry (METI).

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

• gbizcompanysearch(name?, prefecture?, city?, corporatetype?, has?, capitalmin?, capitalmax?, employeesmin?, employeesmax?, foundedyear?, limit?, page?, _apiKey) — find companies and their corporate numbers.
• gbizcompanyprofile(corporatenumber, apiKey) — registry profile: legal name, kana and romanised forms, address, representative director, capital, headcount, establishment date, business summary, website, dissolution.
• gbizcompanyprocurement(corporatenumber, limit?, apiKey) — Japanese government contracts awarded: order date, title, amount in yen, awarding ministry.
• gbizcompanysubsidies(corporatenumber, limit?, apiKey) — subsidies and grants received: approval date, programme, amount, granting ministry.
• gbizcompanyrecords(corporatenumber, kind, limit?, apiKey) — patent, certification, commendation, finance or workplace.

The five kinds do not share one response shape. patent, certification and commendation come back as a LIST under a key matching the kind, with returned and totalonrecord counts. finance and workplace are ONE record per company, so they come back as an OBJECT — finance under finance (accounting standards, the fiscal-year cover page, a managementindex period series and majorshareholders), and workplace statistics under workplaceinfo, whose key deliberately does not match its workplace kind because that is what the upstream returns. For the object kinds limit caps the arrays nested inside, and totalon_record is a per-array map rather than a single number.

Auth

Platform key, since 2026-09-13 (fleet #1940). The gateway holds PLATFORMGBIZINFOKEY and injects it, so callers need no key of their own. _apiKey is still accepted for anyone who would rather use their own token and its own quota.

It shipped BYOK-only first, with platformKeyEnv deliberately absent, so the gateway's keyBlockedTools() sank these tools from routing while no key existed — an honest no_match beats routing Japanese-company questions to a tool that can only refuse. The secret and platformKeyEnv landed in the same change, which is the rule that ordering exists to enforce (the fda-inspections precedent, fleet #617).

To use your own token, register free at . A non-Japanese applicant can register: the form's 利用者区分 radio offers 法人担当者 (corporate — wants a 13-digit 法人番号, Japanese company name, department, postcode, address and phone) and 個人利用者 (individual), for which the required fields are just email, password, purpose and the two consent boxes. This is the distinction that makes gBizINFO usable where the NTA 法人番号 API is not — that one's application path requires a Japanese corporate number with no individual alternative. The token arrives by email.

The public OpenAPI document at https://api.info.gbiz.go.jp/hojin/v3/api-docs?group=v2 embeds a token in info.description. The same sentence says, in Japanese, that it is for checking behaviour on the Swagger page only. It is useful for reading response shapes while building. It is not a credential to ship, and this pack does not carry it.

Upstream behaviour worth knowing

Shortened. The full README is on GitHub.