jp-data-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTA_APP_ID | No | Optional NTA Web-API application ID used for live corporate registry data. Without it, lookup_corporate_number and search_corporations_by_name fall back to synthetic sample data. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_corporate_numberA | 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). |
| lookup_corporate_numberA | 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). |
| search_corporations_by_nameA | Search corporations by (partial) name. Live NTA Web-API when NTA_APP_ID is set; otherwise searches the bundled SYNTHETIC sample set. |
| lookup_bankA | Look up a Japanese bank by its 4-digit zengin bank code (統一金融機関コード). Returns name / kana / hiragana / romaji. |
| search_banksA | Search Japanese banks by name fragment (kanji / kana / hiragana / romaji all matched). Returns zengin codes + names. |
| lookup_branchA | 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. |
| japan_holidaysB | List Japanese national holidays for a year (official Cabinet Office syukujitsu.csv, bundled). |
| is_japan_holidayA | Check whether a date (YYYY-MM-DD) is a Japanese national holiday. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: corporate number validation vs enrichment vs search, bank lookup vs search, branch lookup, and holiday list vs date check. The validate tool explicitly points to lookup for registry confirmation, eliminating any ambiguity.
Six of eight tools follow a consistent verb_noun pattern (lookup_bank, search_banks, lookup_branch, etc.), but the holiday tools deviate with japan_holidays (a noun) and is_japan_holiday (is_ prefix). Minor pluralization inconsistency (search_banks vs lookup_bank) is acceptable.
Eight tools is well-scoped for a Japan data server covering corporate registry, banking, and holidays. Each tool serves a distinct purpose and there is no redundancy.
The corporate domain has validate, lookup, and search; banking has bank/branch lookup plus search; holidays have list and check. Workflows like search-to-validate-to-lookup are supported, and there are no obvious gaps or dead ends.