JP Data (Japanese Public Business Data)
MCPB · JP-DATA-MCP-0.1.0.MCPB
Japanese open-data MCP server: corporate-number validation, zengin bank codes, national holidays
Available components
Last scanned (22 hours ago)
Scores higher than 82% of MCPB servers
Category Finance and Payments
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 Security12
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 22 of 22 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Install-script risk not yet assessed.Unverified
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 91 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 495 tokens (~61/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
- Maintenance: unverified → pass ▲ functional
- 3 Nov 26 −5
- Stability: pass → 0.63 functional
- 2 Nov 26 −1
- Maintenance: pass → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed mcpb/https://github.com/kimotostudio/jp-data-mcp/releases/download/v0.1.0/jp-data-mcp-0.1.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
is_japan_holiday Is Japan Holiday ~33
Check whether a date (YYYY-MM-DD) is a Japanese national holiday.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
japan_holidays Japan Holidays ~36
List Japanese national holidays for a year (official Cabinet Office syukujitsu.csv, bundled).
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_bank Lookup Bank ~50
Look up a Japanese bank by its 4-digit zengin bank code (統一金融機関コード). Returns name / kana / hiragana / romaji.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_code | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_branch Lookup Branch ~65
Look up a bank branch by 4-digit bank code + 3-digit branch code (支店コード). Branch data is lazily fetched from the public zengin-code dataset and cached locally.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_code | string | yes | – |
| branch_code | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_corporate_number Lookup Corporate Number ~72
Enrich a 13-digit corporate number with registry data (name, address, kind, dates). Uses the NTA 法人番号 Web-API when NTA_APP_ID is set; otherwise falls back to bundled SYNTHETIC sample data (clearly tagged).
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_banks Search Banks ~51
Search Japanese banks by name fragment (kanji / kana / hiragana / romaji all matched). Returns zengin codes + names.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_corporations_by_name Search Corporations By Name ~61
Search corporations by (partial) name. Live NTA Web-API when NTA_APP_ID is set; otherwise searches the bundled SYNTHETIC sample set.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_corporate_number Validate Corporate Number ~61
Validate a 13-digit Japanese corporate number (法人番号) offline: format + official NTA check-digit formula. Does NOT confirm the company exists in the registry (use lookup_corporate_number for that).
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the JP Data (Japanese Public Business Data) MCP server?
JP Data (Japanese Public Business Data) ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · jp-data-mcp-0.1.0.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the JP Data (Japanese Public Business Data) MCP server?
JP Data (Japanese Public Business Data) is an MCP server listed in the public MCP registry as io.github.kimotostudio/jp-data-mcp. Japanese open-data MCP server: corporate-number validation, zengin bank codes, national holidays. This page covers its MCPB bundle (https://github.com/kimotostudio/jp-data-mcp/releases/download/v0.1.0/jp-data-mcp-0.1.0.mcpb).
Is the JP Data (Japanese Public Business Data) MCP server safe to use?
JP Data (Japanese Public Business Data) scores 51 out of 100 on VerifyMCP. 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 JP Data (Japanese Public Business Data) MCP server expose?
JP Data (Japanese Public Business Data) exposes 8 tools: validate_corporate_number, lookup_corporate_number, search_corporations_by_name, lookup_bank, search_banks, and 3 more. Their descriptions and schemas cost roughly 429 tokens of context every time the server is loaded.
What licence is the JP Data (Japanese Public Business Data) MCP server under?
JP Data (Japanese Public Business Data) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.