Torify — Japan Locale APIs for AI Agents MCP Server

by torify Your server? Claim it

answering

Torify — Japan Locale APIs for AI Agents is answering right now. Last checked 14 min ago. It exposes 24 tools. Last commit 29 May 2026.

39 Japanese locale APIs — wareki, NTA invoice, 法人番号, postal, romanization, kanji-kana (Workers AI).

Uptime history 51 days of history · worst day 0%

51 days agonow

100.0%

Uptime 24h

11 of 11 checks

Tools

read from the server

469 ms

Response time

average over 24h

Stars

last commit 29 May 2026

What changed 45

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

22 Sep the owner changed

21 Sep the owner changed

20 Sep the owner changed

19 Sep the owner changed

18 Sep the owner changed

17 Sep the owner changed

16 Sep the owner changed

15 Sep the owner changed

14 Sep the owner changed

13 Sep the owner changed

and 35 more, back to 9 August 2026

Torify — Japan Locale APIs for AI Agents does not always answer

Over the last week it answered 83.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add japanese-locale-mcp --transport http https://torify-mcp.torify.workers.dev

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "japanese-locale-mcp": {
      "url": "https://torify-mcp.torify.workers.dev"
    }
  }
}

~/.codex/config.toml

[mcp_servers.japanese-locale-mcp]
url = "https://torify-mcp.torify.workers.dev"

.cursor/mcp.json

{
  "mcpServers": {
    "japanese-locale-mcp": {
      "url": "https://torify-mcp.torify.workers.dev"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "japanese-locale-mcp": {
      "url": "https://torify-mcp.torify.workers.dev"
    }
  }
}

Available tools 24

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

torify

torify_company.fullProfile

One-call composite: 13-digit corporate number (法人番号) → company name, address, kind, status (NTA 法人番号 API) + optional invoice registration check (NTA 適格請求書 API). 日本語: 法人番号 1 つで法人情報とインボイス登録状態を同時取得。**Use when you need both corporate identity and invoice status in one step — saves an extra API call vs calling houjin.lookup + invoice.verify separately.** Note: government agencies (e.g. NTA itself) often return invoiceStatus.registered=false — this is correct per Japanese tax law. [Torify namespace — official]

torify_geo.geocode

Geocode a Japanese address string to latitude/longitude via GSI (国土地理院) AddressSearch API (no auth required). Address format only — landmark names and station names are not supported. 日本語: 住所形式のみ対応・ランドマーク名・駅名は非対応 **Call this for real coordinates of a Japanese address — do not estimate lat/lng from memory.** [Torify namespace — official]

torify_geo.reverseGeocode

Reverse geocode lat/lng to municipality code and town name via GSI (国土地理院) reverse-geocoder API. 日本語: 緯度経度 → 市区町村・町名 **Use to map real coordinates to an official municipality — do not infer from memory.** [Torify namespace — official]

torify_houjin.lookup

Look up Japanese corporate number (法人番号, 13 digits) → company name, address, kind, and status via NTA official API. 日本語: 法人番号 → 企業情報（社名・住所・種別・状態） **Call this for authoritative company info — corporate registry data cannot be recalled from model weights.** [Torify namespace — official]

torify_invoice.companyProfile

One-call composite: T-number (T + 13 digits) → invoice registration status (NTA 適格請求書 API) + corporate details (NTA 法人番号 API). 日本語: T番号 1 つでインボイス登録状態と法人詳細を同時取得。**Use when an AI agent receives a T-number (e.g. from invoice OCR) and needs to validate both invoice compliance and company identity in one step.** Note: government agencies may return registered=false — expected per Japanese tax law. [Torify namespace — official]

torify_invoice.validate

Validate Japanese qualified invoice number (T-number) format and check digit. T + 13 digits. 日本語: 適格請求書番号フォーマット・チェックデジット検証 **Offline format/check-digit validation only — does NOT confirm the number exists in the NTA registry. To verify real registration, use invoice.verify.** [Torify namespace — official]

torify_invoice.verify

Verify invoice number registration against NTA public registry API. Returns registrant name, address, and registration date. Requires INVOICE_APP_ID (free, apply via NTA). 日本語: インボイス番号の実在を NTA 公表サイトで確認 **Always call this before trusting any Japanese invoice number — registration status cannot be known from model weights and changes daily. For offline format checks only, use invoice.validate.** [Torify namespace — official]

torify_kanji.toKana

Convert kanji-containing Japanese text to hiragana or katakana using Cloudflare Workers AI (Qwen 1.5 14B, Japanese/Chinese optimized). 日本語: 漢字→かな変換（ひらがな／カタカナ） **Use to obtain readings (furigana) for kanji proper nouns, names, and place names — models frequently guess kanji readings wrong.** [Torify namespace — official]

torify_law.search

Search Japanese laws by title via e-Gov Hourei API v2 (no auth required). Returns law ID, number, title, and promulgation date. 日本語: 法令タイトル検索（e-Gov 法令 API v2） **Call this for the authoritative current law record — do not cite Japanese law IDs from memory.** [Torify namespace — official]

torify_name.romanize

Hepburn romanize Japanese names (katakana/hiragana) in passport style. Supports family-first and given-first order. 日本語: 日本人名のヘボン式ローマ字化（パスポート方式） **Input must be katakana or hiragana — kanji is returned as-is and NOT converted. To get readings of kanji names, call kanji.toKana first.** [Torify namespace — official]

torify_postal.lookup

Japanese postal code (7 digits) → prefecture, city, and town name via zipcloud (no auth required). 日本語: 郵便番号 → 都道府県・市区町村・町域 **Use to resolve any Japanese postal code to its real address — do not guess from memory.** [Torify namespace — official]

torify_wareki.convert

Convert between Japanese era dates (wareki) and Gregorian. Supports Meiji/Taisho/Showa/Heisei/Reiwa. Handles era boundary dates accurately. 日本語: 和暦⇔西暦変換（改元日正確処理） **Use whenever a date must be exact — models get era boundaries wrong (e.g. Showa 64 = Jan 1-7 1989 only). Do not compute wareki from memory.** [Torify namespace — official]

invoice

invoice.companyProfile

invoice.validate

invoice.verify

geo

geo.geocode

geo.reverseGeocode

company

company.fullProfile

houjin

houjin.lookup

kanji

kanji.toKana

law

law.search

name

name.romanize

postal

postal.lookup

wareki

wareki.convert

Endpoints

URL	Transport	State	Latency	Checked
https://torify-mcp.torify.workers.dev	streamable-http	answering	609 ms	14 min ago

Alternatives to Torify — Japan Locale APIs for AI Agents

same job, measured the same way

Extract

by mart402

Web extraction, OCR (Japanese-strong), invoice and company data for AI agents. x402, no API key.

35 tools answering

MCP Jp Doc Intel

by infoinlet-marketplace

Japanese document AI for agents — invoice/meishi extraction, OCR, classification (hosted API).

15 installs/wk local only

MCP Jp Corporate ID

by skypier-jp-works

Validates and normalizes Japanese corporate numbers and invoice registration numbers (format only).

24 installs/wk local only

Karbon MCP Server

by mad-man-dan

Unofficial MCP server for Karbon practice management: contacts, work, time, invoices, payments.

54 installs/wk local only

Jp Crypto Tax Rules

by kodandy

Machine-readable Japanese crypto-asset tax rules for AI agents: rules-as-code with citations, x402.

4 tools answering

Work Order

by theluckystrike

Job orders for trades and field work: parts, labour, status, completion report, invoice payload.

12 tools answering

BTCPay Server MCP

by draket

21 tools for AI agents to manage BTCPay Server: invoices, payments, stores, webhooks, Lightning

local only

Invoiceflow MCP

by enzoemir1

AI-powered invoice automation. Create invoices, track payments, and manage cash flow.

43 installs/wk local only

Torify — Japan Locale APIs for AI Agents — questions

Answers built from our own checks of this server.

What can Torify — Japan Locale APIs for AI Agents do?

It exposes 24 tools, read directly from the server on our last check. Among them: company.fullProfile, geo.geocode, geo.reverseGeocode, houjin.lookup, invoice.companyProfile, invoice.validate and 18 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Torify — Japan Locale APIs for AI Agents mostly used for?

Its tools cluster around torify, invoice and geo. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Torify — Japan Locale APIs for AI Agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 11 of 11 checks got a reply (100.0%), average response time 469 ms. The bar chart above shows every period we have measured.

How do I connect Torify — Japan Locale APIs for AI Agents?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Torify — Japan Locale APIs for AI Agents need an API key?

No. Torify — Japan Locale APIs for AI Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 24 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Torify — Japan Locale APIs for AI Agents?

It answers our handshake in 469 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Torify — Japan Locale APIs for AI Agents open source?

Yes — it is published under the MIT licence, written in Shell, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.