Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Gbizinfo

NPM · @PIPEWORX/MCP-GBIZINFO · 2 COMPONENTS

gBizINFO — Japanese corporate registry, from METI (経済産業省).

+4 this week 82 Trust /100

Last scanned (3 hours ago)

Scores higher than 72% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-gbizinfo). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1443 tokens (~288/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 2 Nov 26 +2
    • Security disclosure: fail → unverified ▼ functional
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 78

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-gbizinfo@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-gbizinfo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-gbizinfo/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637321702
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:f28f7d7d72a9d195615a110262459bcfa092b5eba48c7123ae0f048d133a31883f7db5b85bb8312d6b0547910f91891832e22e375f098350ad24bac5d

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,389 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
gbiz_company_procurement ~203

Japanese government contracts awarded to one company, by its 13-digit corporate number, from gBizINFO (METI). Each award returns the order date, the contract title, the amount in yen and the ministry or agency that placed it — the Japanese counterpart to a USAspending award history.

NameTypeReqDescription
_apiKeystring–Optional. Your own gBizINFO API token, if you would rather use your own quota than the shared one. Register free at https://info.gbiz.go.jp/hojin/various_registration/form — pick 個人利用者 (individual) u…
corporate_numberstringyesThe company: its 13-digit Japanese corporate number (法人番号) or its name — a name is resolved, and the Japanese form resolves far more reliably than a romanised one.
limitnumber–Awards to return, newest first, 1-500 (default 50).

No output schema declared.

No examples provided.

gbiz_company_profile ~220

Registry profile for one Japanese company by its 13-digit corporate number (法人番号), from gBizINFO (METI). Returns the Japanese legal name, kana and romanised forms, registered address and postcode, representative director, capital stock in yen, employee count, date of establishment, business summary and corporate website, plus dissolution date if the company has closed.

NameTypeReqDescription
_apiKeystring–Optional. Your own gBizINFO API token, if you would rather use your own quota than the shared one. Register free at https://info.gbiz.go.jp/hojin/various_registration/form — pick 個人利用者 (individual) u…
corporate_numberstringyesThe company: its 13-digit Japanese corporate number (法人番号), e.g. "1180301018771", or its name. A name is resolved to a corporate number, and the Japanese name resolves far more reliably than a romani…

No output schema declared.

No examples provided.

gbiz_company_records ~292

Patents and trademarks, statutory certifications, government commendations, filed financial results, or workplace statistics for one Japanese company, by its 13-digit corporate number, from gBizINFO (METI). Pick the record type with `kind`. Workplace statistics carry headcount by sex, average tenure, average age, overtime hours and childcare-leave take-up — the disclosure Japanese employers file under the 女性活躍推進法.

NameTypeReqDescription
_apiKeystring–Optional. Your own gBizINFO API token, if you would rather use your own quota than the shared one. Register free at https://info.gbiz.go.jp/hojin/various_registration/form — pick 個人利用者 (individual) u…
corporate_numberstringyesThe company: its 13-digit Japanese corporate number (法人番号) or its name — a name is resolved, and the Japanese form resolves far more reliably than a romanised one.
kindstringyesWhich record set: "patent", "certification", "commendation", "finance" or "workplace".
limitnumber–Records to return, 1-500 (default 50). For "finance" and "workplace", which are one record per company rather than a list, this caps the arrays nested inside it (e.g. the financial period series).

No output schema declared.

No examples provided.

gbiz_company_search ~481

Find Japanese companies and their 13-digit corporate numbers (法人番号) in gBizINFO, the Japanese government corporate registry run by METI. Search by company name, prefecture, corporate form, capital, employee count, revenue, or by whether the company has government procurement awards, subsidies, patents or filed financials. Returns each match with its corporate number, Japanese legal name, romanised name, registered address, capital and headcount.

NameTypeReqDescription
_apiKeystring–Optional. Your own gBizINFO API token, if you would rather use your own quota than the shared one. Register free at https://info.gbiz.go.jp/hojin/various_registration/form — pick 個人利用者 (individual) u…
capital_maxnumber–Maximum capital stock in yen.
capital_minnumber–Minimum capital stock in yen.
citystring–Municipality code from the same JIS scheme.
corporate_typestring–Corporate form code: 301 株式会社 (joint-stock), 302 有限会社, 303 合名会社, 304 合資会社, 305 合同会社, 201 local government, 101 national body.
employees_maxnumber–Maximum employee count.
employees_minnumber–Minimum employee count.
founded_yearstring–Year of establishment, or several comma-separated.
hasstring–Restrict to companies that have records of a given kind: procurement, commendation, certification, subsidy, patent, finance.
limitnumber–Companies to return, 1-100 (default 20).
namestring–Company name, partial match. PASS THE JAPANESE NAME WHERE YOU CAN ("トヨタ自動車"): a Latin-script query is matched against the romanised name field, which is sparse and dominated by municipal bodies — "To…
pagenumber–Result page, 1-10 (default 1).
prefecturestring–Prefecture code, 2 digits from the JIS local-government code (13 = Tokyo, 23 = Aichi, 27 = Osaka).

No output schema declared.

No examples provided.

gbiz_company_subsidies ~193

Japanese government subsidies and grants received by one company, by its 13-digit corporate number, from gBizINFO (METI). Each record returns the approval date, the subsidy programme name, the amount in yen and the granting ministry.

NameTypeReqDescription
_apiKeystring–Optional. Your own gBizINFO API token, if you would rather use your own quota than the shared one. Register free at https://info.gbiz.go.jp/hojin/various_registration/form — pick 個人利用者 (individual) u…
corporate_numberstringyesThe company: its 13-digit Japanese corporate number (法人番号) or its name — a name is resolved, and the Japanese form resolves far more reliably than a romanised one.
limitnumber–Subsidies to return, newest first, 1-500 (default 50).

No output schema declared.

No examples provided.

Install

How do I install the Gbizinfo MCP server?

Gbizinfo runs locally as an npm package, launched with npx -y @pipeworx/mcp-gbizinfo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-gbizinfo

# add to Claude Code
claude mcp add pipeworx-io-gbizinfo -- npx -y @pipeworx/mcp-gbizinfo
Common questions

What is the Gbizinfo MCP server?

Gbizinfo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/gbizinfo. gBizINFO, Japanese corporate registry, from METI (経済産業省). This page covers its npm package (@pipeworx/mcp-gbizinfo).

Is the Gbizinfo MCP server safe to use?

Gbizinfo scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Gbizinfo MCP server expose?

Gbizinfo exposes 5 tools: gbiz_company_search, gbiz_company_profile, gbiz_company_procurement, gbiz_company_subsidies, gbiz_company_records. Their descriptions and schemas cost roughly 1,389 tokens of context every time the server is loaded.

Is the Gbizinfo MCP server still maintained?

Gbizinfo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Gbizinfo MCP server under?

Gbizinfo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.