Skip to main content
Glama

JP Zengin Name

Format, check and compare Japanese bank-transfer account names (振込名義・口座名義カナ) the way Japanese banks accept them. MCP server, CLI and Python library. Standard library only, no network, MIT.

A Japanese bank transfer carries the payee and payer name in a restricted set: half-width katakana, digits, A-Z, a few symbols and a half-width space. Small kana are written large, ー becomes -, ・ becomes ., and words like 株式会社 are replaced by an abbreviation whose parentheses depend on where the word sits: カ) at the start, (カ) in the middle, (カ at the end (rules as published by one broker). Get one of these wrong and the transfer file is rejected. Accounting software reports it as 「振込依頼人名に使用できない文字が含まれています。」 (example FAQ).

A language model asked to "convert to half-width kana" usually keeps the small kana, writes 株式会社 out in full, and counts ガ as one character when the bank counts two (ガ).

株式会社 ガイタメドットコム                 -> カ)ガイタメドツトコム
ガイタメドットコム株式会社 オキナワシシャ    -> ガイタメドツトコム(カ)オキナワシシヤ
かぶしきがいしゃ にっぽんしょうじ           -> カ)ニツポンシヨウジ
合同会社 ネクサス・ツールズ                 -> ド)ネクサス.ツ-ルズ
キャット・フード                           -> キヤツト.フ-ド
山田 タロウ                                -> error E_KANJI_NEEDS_READING (chars: 山田)

What it does:

  • maps 59 legal-entity, branch and business words (株式会社, 合同会社, 医療法人, 一般社団法人, 特定非営利活動法人, 営業所, 健康保険組合 ...) to the bank abbreviation with the start / middle / end rule, also when spelled out in kana (カブシキガイシャ)

  • makes small kana large, converts hiragana, full-width letters and digits, ー ・ and full-width spaces

  • returns the half-width form for the transfer file and a full-width form for display

  • counts length the way the file does (a voiced kana is two characters) and warns above 30 (configurable)

  • refuses kanji other than entity words and tells you which characters need a reading. It never guesses a reading

  • compares a statement name with a customer name for reconciliation (入金消込), ignoring abbreviations, spaces, punctuation and width, and tells you when the entity type differs (ユ) vs 株式会社)

Every message comes in English and Japanese.

Use as an Agent Skill

SKILL.md tells the agent to call the formatter instead of converting names by hand. Add it with the skills CLI: npx skills add japan-ai-tools/jp-zengin-name (it reads the SKILL.md at the repository root). / スキルとして入れるなら npx skills add japan-ai-tools/jp-zengin-name。

Related MCP server: jp-business-calendar-mcp

MCP server (for AI agents)

Protocol: the stdio server speaks both MCP 2026-07-28 (stateless: server/discover, version and capabilities in each request's _meta, no initialize) and the older initialize flow (2025-06-18, 2025-03-26, 2024-11-05). Tests: tests/test_mcp_2026.py. 新しい MCP 2026-07-28(握手なし)と従来の initialize の両方で動きます。

{"mcpServers": {"jp-zengin-name": {"command": "python", "args": ["-m", "zenginname.server"], "cwd": "/path/to/jp-zengin-name"}}}

Tool

Input

Returns

zengin_name_format

name (kana reading), max_length

ok, zengin, display, length, entities, changes, errors, warnings

zengin_name_check

name (half-width), max_length

ok, length, errors, warnings, abbreviations

zengin_name_match

a, b

match, name_match, key_a, key_b, entity_a, entity_b, entity_type_differs

All tools are read-only and offline.

CLI and Python

python -m zenginname "株式会社 にっぽんしょうじ"     # JSON, exit 1 on error
python -m zenginname --file names.txt               # TSV: input, zengin, ok/NG, codes
python -m zenginname.bench                          # score on the 30 test cases
from zenginname import format_name, check_name, match_names
format_name("ホシ 税理士法人")["zengin"]        # 'ホシ(ゼイ'
check_name("カ)ニッポン")["errors"][0]["code"]     # 'E_SMALL_KANA'
match_names("カ)サクラ", "サクラ株式会社")["match"]  # True

Test cases

data/zengin_name_cases_v1.jsonl has 30 inputs and expected outputs (entity positions, spelled entities, small kana, width, ヴ, old kana, split dakuten). This package scores 30/30. A naive converter (NFKC, hiragana to katakana, katakana to half-width) scores 2/30. The rules and the cases were written together, so 30/30 shows consistency with the published rules, not accuracy on real bank files. Corrections from people who send transfers are welcome as Issues.

Codes

Errors: E_EMPTY E_KANJI_NEEDS_READING E_CHAR_NOT_ALLOWED E_SMALL_KANA. Warnings: W_TOO_LONG W_MERGED_ROW W_ENTITY_ONLY W_PARENS W_SPACES.

Limits

  • It does not read kanji. Pass the reading (the agent should ask the user or use the reading on file).

  • Banks differ in details (maximum length, some symbols). Rows that are blank in the source table (医療法人社団, 公益財団法人, 公立大学法人 ...) use the abbreviation of the row above and return W_MERGED_ROW; confirm with your bank.

  • It formats names only. It does not handle account numbers, bank codes or money.


日本語

振込名義(口座名義カナ)を、銀行の振込で通る形(全銀の半角カナ)に整える道具です。小さいカナを大きく、ー→-、・→.、株式会社などは位置で変わる略語(先頭 カ)・途中 (カ)・末尾 (カ)にします。濁点は1文字に数えて字数を確かめます。漢字の読みは推測しません(法人の種類の言葉だけ変換し、ほかの漢字は E_KANJI_NEEDS_READING で返します)。入金消込で、通帳の名義と取引先名が同じかも比べられます。標準ライブラリだけ・外部通信なし・MIT。

  • If you keep a supplier list for transfers, invoice-watch compares it with the NTA's published invoice-registration data and reports only the suppliers whose registration was cancelled, expired or renamed.

関連(同じ作者): 振込先の取引先の一覧があるなら、取引先インボイス見張り(invoice-watch) が国税庁の公表データと照らして、登録の取消・失効・名称の変化だけを知らせます。

Available Tools

3 tools
zengin_name_checkCheck an already formatted half-width transfer nameB
Read-onlyIdempotent

Validate a half-width Zengin name from a CSV or bank file: only allowed characters, no small kana, no full-width characters, spacing, length. Returns ok, length, errors, warnings, abbreviations found.

Inputs: name (required), max_length.

zengin_name_formatFormat a Japanese bank-transfer account name (振込名義カナ)A
Read-onlyIdempotent

Turn a payee or payer name into the form Japanese banks accept in transfers (Zengin): half-width katakana, digits, A-Z and a few symbols; small kana made large (ッ->ツ, ャ->ヤ), ー->-, ・->., legal-entity words replaced by the bank abbreviation with the position rule (株式会社 at the start 'カ)', in the middle '(カ)', at the end '(カ'). Accepts kana (hiragana or katakana, full or half width), Latin letters and digits, and legal-entity words in kanji or spelled out (カブシキガイシャ). It does NOT read other kanji: pass the reading. Returns ok, zengin (half-width), display (full-width), length (voiced kana count 2), entities, changes, errors, warnings (code, message in English and Japanese). 振込名義を全銀の形に整える。

Inputs: name (required), max_length.

zengin_name_matchCompare two names for payment reconciliation (入金消込)A
Read-onlyIdempotent

Decide whether a payer name on a bank statement (half-width, abbreviated) and a customer name (kana reading) are the same, ignoring entity abbreviations, spaces, punctuation, small/large kana and width. Returns match, name_match, key_a, key_b, entity_a, entity_b, entity_type_differs (e.g. ユ) vs 株式会社), errors.

Inputs: a (required), b (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct action on Zengin names: matching two names, formatting a name into Zengin form, and validating an existing Zengin name. The boundaries between format (produce) and check (validate) are clear from the descriptions, so an agent can select the right tool without ambiguity.

    Naming Consistency5/5

    All three tools follow the same predictable pattern: a shared `zengin_name_` prefix plus a distinct action verb (`match`, `format`, `check`). There is no mixing of conventions or vague verbs.

    Tool Count5/5

    Three tools are well-scoped for a narrow domain focused on Japanese Zengin name handling. Each tool covers a distinct operation and none feels redundant or missing for the stated purpose.

    Completeness5/5

    The surface covers the core lifecycle: match payer/customer names, format names to Zengin standards, and validate Zengin names from files. Together these operations form a complete workflow for the domain without obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Japan-specific utilities for AI agents — era ↔ Western year conversion, kanji-to-romaji, postal code lookup, national holidays, kana conversion, and Japanese name splitting. 9 tools, MIT licensed, install via uvx.
      9
      29 PyPI
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform Japanese business calendar calculations including holiday detection, business day arithmetic, payment date settlement, and deadline management using local data.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to validate a Japanese qualified invoice against the six required items, reduced-rate markings, per-rate totals, and once-per-invoice-per-rate tax rounding, while flagging the common line-by-line rounding mistake, and to normalize and verify T + 13-digit registration numbers. Read-only tools also compute expected consumption tax for a given amount, rate, price basis, and rounding method.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to identify Japanese companies by name, look up corporate numbers, addresses, and qualified invoice registration status, and batch-match company lists using read-only tools.
      4
      60 npm
      MIT