Torify — Japan Locale APIs For AI Agents
Call 39 Japan-specific locale APIs—wareki, invoices, corporate numbers, postal codes, romanization, and kanji–kana—from your agent while building JP-facing products.
Overview
dev.torify/japanese-locale-mcp is an MCP server for the Build phase that exposes 39 Japanese locale APIs—including wareki, NTA invoice, corporate number, postal, romanization, and kanji-kana—for AI-driven integrations.
What is this MCP server?
- 39 Japanese locale API surfaces exposed via MCP (streamable HTTP on Cloudflare Workers)
- Covers wareki, NTA invoice, 法人番号 (corporate number), postal, romanization, kanji-kana with Workers AI
- Remote endpoint: torify-mcp.torify.workers.dev
- Version 0.2.0 with examples in endennn/torify-examples on GitHub
- Built for AI agents shipping Japan-market SaaS, ecommerce, or internal tools
- 39 Japanese locale API surfaces advertised in server description
- MCP server version 0.2.0
- Remote type: streamable-http on Cloudflare Workers
What problem does it solve?
Shipping Japan-ready forms, invoices, and search without reimplementing wareki, 法人番号, postal, and kana rules forces endless tab-switching between docs and ad hoc scripts.
Who is it for?
Solo builders and small teams building JP-facing SaaS, APIs, or ecommerce who want agent-callable locale APIs instead of manual API hunting.
Skip if: Products with no Japan audience, or teams that need full legal/tax advisory rather than programmatic locale helpers.
What do I get? / Deliverables
After you connect the remote MCP URL, your agent can pull normalized Japanese locale data and conversions while you build integrations in one repo session.
- Structured locale API responses wired into your JP-facing features
- Faster agent-assisted implementation of postal, invoice, and text-normalization flows
Recommended MCP Servers
Journey fit
Locale and compliance APIs are wired during product construction, so Build / integrations is the canonical shelf for JP market features. Integrations subphase is where you connect external data services (postal, NTA, romanization) into forms, billing, and search.
How it compares
MCP locale API aggregator for Japan, not a general i18n string catalog skill.
Common Questions / FAQ
Who is dev.torify/japanese-locale-mcp for?
It is for developers using AI coding assistants who are building software for Japanese users and need wareki, invoice, corporate ID, postal, and text-normalization APIs in one MCP server.
When should I use dev.torify/japanese-locale-mcp?
Use it during Build when you implement address lookup, qualified invoice fields, company lookup, or kana/romanization in features aimed at the Japan market.
How do I add dev.torify/japanese-locale-mcp to my agent?
Add the streamable-http remote https://torify-mcp.torify.workers.dev from the server schema to your MCP client, then call the documented tools from Claude Code, Cursor, or a compatible agent.