Torify — Japan Locale APIs for AI Agents
REMOTE · TORIFY-MCP.TORIFY.WORKERS.DEV
39 Japanese locale APIs — wareki, NTA invoice, 法人番号, postal, romanization, kanji-kana (Workers AI).
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 16 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 24 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: 203 → 160 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: fail → 0.70 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Aug 26 0
- Stability: 0.63 → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 160 → 203 ▼ functional
- Schema quality: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://torify-mcp.torify.workers.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=torify.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5aca88339c81b118f1c78497bff4644c39f |
| SANs: *.torify.workers.dev, torify.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of torify-mcp.torify.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://torify-mcp.torify.workers.dev | HTTP error | 404 | |
| http (plaintext) | http://torify-mcp.torify.workers.dev | Inconclusive | 404 |
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 →
company.fullProfile Company Full Profile (Corporate + Invoice) ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 法人番号（13桁の数字、例: 1180301018771） |
| verify_invoice | string | – | true のとき対応するT番号（T+法人番号）のインボイス登録状態も確認する（デフォルト: false） |
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | 住所 |
| confidence | number | yes | 信頼度スコア（0〜0.99） |
| houjinBangou | string | yes | 法人番号（13桁） |
| invoiceStatus | object | – | インボイス登録状態（verify_invoice=true のときのみ） |
| kind | object | – | 法人種別 |
| name | string | yes | 法人名 |
| nameEn | string | – | 法人名（英語） |
| nameKana | string | – | 法人名（フリガナ） |
| sources | array | yes | データソース一覧 |
| status | string | yes | 法人状態 |
| verified_at | string | yes | 確認日時（ISO 8601） |
No examples provided.
geo.geocode Japan Address Geocoder ~162
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Japanese address string in address format (e.g. 東京都千代田区丸の内一丁目). Landmark/station names (e.g. 東京駅) are not supported. / 住所形式（例: 東京都千代田区丸の内一丁目）。ランドマーク名・駅名は非対応 |
| Name | Type | Req | Description |
|---|---|---|---|
| addressCode | string | yes | 住所コード |
| lat | number | yes | 緯度 |
| lng | number | yes | 経度 |
| source | string | yes | データソース |
| title | string | yes | 正規化住所 |
No examples provided.
geo.reverseGeocode Japan Reverse Geocoder ~108
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | 緯度（日本領域: 20-46） |
| lon | number | yes | 経度（日本領域: 122-154） |
| Name | Type | Req | Description |
|---|---|---|---|
| muniCode | string | yes | 市区町村コード |
| source | string | yes | データソース |
| town | string | yes | 町名 |
No examples provided.
houjin.lookup Japanese Corporate Number Lookup ~103
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 法人番号（13桁の数字、例: 7000012050002） |
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | 住所 |
| houjinBangou | string | yes | 法人番号（13桁） |
| kind | object | – | 法人種別 |
| lastUpdated | string | – | 最終更新日 |
| name | string | yes | 法人名 |
| nameEn | string | – | 法人名（英語） |
| nameKana | string | – | 法人名（フリガナ） |
| source | string | yes | データソース |
| status | string | yes | 法人状態 |
No examples provided.
invoice.companyProfile Invoice T-number → Company Profile (Invoice + Corporate) ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | インボイス番号（T + 13桁、例: T1180301018771） |
| Name | Type | Req | Description |
|---|---|---|---|
| cancelDate | – | – | 取消日（null の場合は未取消） |
| confidence | number | yes | 信頼度スコア（0〜0.99） |
| houjin | object | – | 法人詳細（registered=true のときに取得） |
| invoiceNumber | string | yes | T番号（T + 13桁） |
| registered | boolean | yes | 適格請求書発行事業者として登録されているか |
| registrantAddress | string | – | 登録事業者住所 |
| registrantAddressEn | string | – | 登録事業者住所（英語） |
| registrantName | string | – | 登録事業者名 |
| registrantNameEn | string | – | 登録事業者名（ローマ字） |
| registrationDate | string | – | 登録日 |
| sources | array | yes | データソース一覧 |
No examples provided.
invoice.validate Invoice Number Format Validator ~98
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | インボイス番号（例: T7000012050002） |
| Name | Type | Req | Description |
|---|---|---|---|
| checkDigit | object | – | チェックデジット詳細 |
| format | string | yes | バリデーション結果コード |
| houjinBangou | string | – | T を除いた13桁の法人番号部分 |
| input | string | yes | 入力値 |
| type | string | – | 番号種別 |
| valid | boolean | yes | フォーマットおよびチェックデジットが正しいか |
No examples provided.
invoice.verify Invoice Number NTA Verification ~115
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | インボイス番号（例: T7000012050002） |
| Name | Type | Req | Description |
|---|---|---|---|
| cancelDate | – | – | 取消日（nullの場合は未取消） |
| disclaimer | string | – | 国税庁利用規約に基づく免責表示 |
| input | string | yes | 入力値 |
| registered | boolean | yes | 登録されているか |
| registrantAddress | string | – | 登録事業者住所 |
| registrantName | string | – | 登録事業者名 |
| registrationDate | string | – | 登録日 |
| source | string | yes | データソース |
No examples provided.
kanji.toKana Kanji to Kana Converter ~129
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| output | string | – | 出力形式（既定: hiragana） |
| text | string | yes | 変換するテキスト（最大500文字） |
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | 入力テキスト |
| kana | string | yes | ひらがな/カタカナ変換結果 |
| output | string | yes | 出力形式（hiragana または katakana） |
| source | string | yes | 変換エンジン |
No examples provided.
law.search Japan Law Search ~120
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 取得件数（1-50、既定: 10） |
| title | string | yes | 法令タイトル（部分一致、例: 労働基準法） |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | 取得件数 |
| laws | array | yes | 法令一覧 |
| source | string | yes | データソース |
| total | number | yes | 総ヒット件数 |
No examples provided.
name.romanize Japanese Name Romanizer ~199
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Japanese name in katakana or hiragana. Kanji input is returned as-is (not converted). Add space between family and given name to split parts. / カタカナ必須・漢字入力時は変換されません。姓名の間にスペースを入れると姓/名を分離して変換 |
| order | string | – | family-first: family name first / 姓名順（既定）, given-first: given name first / 名姓順 |
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | 入力値 |
| order | string | – | 適用した名前順序 |
| parts | object | – | 姓名に分離できた場合の各パーツ |
| romaji | string | yes | ローマ字変換結果（例: SUZUKI ICHIRO） |
No examples provided.
postal.lookup Japanese Postal Code Lookup ~108
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| zipcode | string | yes | 郵便番号（7桁、ハイフン任意。例: 1000005 または 100-0005） |
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | yes | Prefecture name / 都道府県名 |
| address2 | string | yes | City/ward/town name / 市区町村名 |
| address3 | string | yes | District/neighborhood name / 町域名 |
| cityEn | – | – | City/ward name in English (romanized) / 市区町村名（英語・ローマ字） |
| kana1 | string | yes | Prefecture name in katakana / 都道府県名（カタカナ） |
| kana2 | string | yes | City/ward/town name in katakana / 市区町村名（カタカナ） |
| kana3 | string | yes | District name in katakana / 町域名（カタカナ） |
| prefcode | string | yes | Prefecture code / 都道府県コード |
| prefectureEn | – | – | Prefecture name in English (e.g. Tokyo) / 都道府県名（英語） |
| townEn | – | – | District name in English (romanized) / 町域名（英語・ローマ字） |
| zipcode | string | yes | Postal code (7 digits) / 郵便番号（7桁） |
No examples provided.
torify_company.fullProfile Company Full Profile (Corporate + Invoice) [Torify namespace — official] ~208
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]
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 法人番号（13桁の数字、例: 1180301018771） |
| verify_invoice | string | – | true のとき対応するT番号（T+法人番号）のインボイス登録状態も確認する（デフォルト: false） |
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | 住所 |
| confidence | number | yes | 信頼度スコア（0〜0.99） |
| houjinBangou | string | yes | 法人番号（13桁） |
| invoiceStatus | object | – | インボイス登録状態（verify_invoice=true のときのみ） |
| kind | object | – | 法人種別 |
| name | string | yes | 法人名 |
| nameEn | string | – | 法人名（英語） |
| nameKana | string | – | 法人名（フリガナ） |
| sources | array | yes | データソース一覧 |
| status | string | yes | 法人状態 |
| verified_at | string | yes | 確認日時（ISO 8601） |
No examples provided.
torify_geo.geocode Japan Address Geocoder [Torify namespace — official] ~171
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]
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Japanese address string in address format (e.g. 東京都千代田区丸の内一丁目). Landmark/station names (e.g. 東京駅) are not supported. / 住所形式（例: 東京都千代田区丸の内一丁目）。ランドマーク名・駅名は非対応 |
| Name | Type | Req | Description |
|---|---|---|---|
| addressCode | string | yes | 住所コード |
| lat | number | yes | 緯度 |
| lng | number | yes | 経度 |
| source | string | yes | データソース |
| title | string | yes | 正規化住所 |
No examples provided.
torify_geo.reverseGeocode Japan Reverse Geocoder [Torify namespace — official] ~117
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]
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | 緯度（日本領域: 20-46） |
| lon | number | yes | 経度（日本領域: 122-154） |
| Name | Type | Req | Description |
|---|---|---|---|
| muniCode | string | yes | 市区町村コード |
| source | string | yes | データソース |
| town | string | yes | 町名 |
No examples provided.
torify_houjin.lookup Japanese Corporate Number Lookup [Torify namespace — official] ~113
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]
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 法人番号（13桁の数字、例: 7000012050002） |
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | 住所 |
| houjinBangou | string | yes | 法人番号（13桁） |
| kind | object | – | 法人種別 |
| lastUpdated | string | – | 最終更新日 |
| name | string | yes | 法人名 |
| nameEn | string | – | 法人名（英語） |
| nameKana | string | – | 法人名（フリガナ） |
| source | string | yes | データソース |
| status | string | yes | 法人状態 |
No examples provided.
torify_invoice.companyProfile Invoice T-number → Company Profile [Torify namespace — official] ~155
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]
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | インボイス番号（T + 13桁、例: T1180301018771） |
| Name | Type | Req | Description |
|---|---|---|---|
| cancelDate | – | – | 取消日（null の場合は未取消） |
| confidence | number | yes | 信頼度スコア（0〜0.99） |
| houjin | object | – | 法人詳細（registered=true のときに取得） |
| invoiceNumber | string | yes | T番号（T + 13桁） |
| registered | boolean | yes | 適格請求書発行事業者として登録されているか |
| registrantAddress | string | – | 登録事業者住所 |
| registrantAddressEn | string | – | 登録事業者住所（英語） |
| registrantName | string | – | 登録事業者名 |
| registrantNameEn | string | – | 登録事業者名（ローマ字） |
| registrationDate | string | – | 登録日 |
| sources | array | yes | データソース一覧 |
No examples provided.
torify_invoice.validate Invoice Number Format Validator [Torify namespace — official] ~107
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]
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | インボイス番号（例: T7000012050002） |
| Name | Type | Req | Description |
|---|---|---|---|
| checkDigit | object | – | チェックデジット詳細 |
| format | string | yes | バリデーション結果コード |
| houjinBangou | string | – | T を除いた13桁の法人番号部分 |
| input | string | yes | 入力値 |
| type | string | – | 番号種別 |
| valid | boolean | yes | フォーマットおよびチェックデジットが正しいか |
No examples provided.
torify_invoice.verify Invoice Number NTA Verification [Torify namespace — official] ~124
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]
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | インボイス番号（例: T7000012050002） |
| Name | Type | Req | Description |
|---|---|---|---|
| cancelDate | – | – | 取消日（nullの場合は未取消） |
| disclaimer | string | – | 国税庁利用規約に基づく免責表示 |
| input | string | yes | 入力値 |
| registered | boolean | yes | 登録されているか |
| registrantAddress | string | – | 登録事業者住所 |
| registrantName | string | – | 登録事業者名 |
| registrationDate | string | – | 登録日 |
| source | string | yes | データソース |
No examples provided.
torify_kanji.toKana Kanji to Kana Converter [Torify namespace — official] ~139
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]
| Name | Type | Req | Description |
|---|---|---|---|
| output | string | – | 出力形式（既定: hiragana） |
| text | string | yes | 変換するテキスト（最大500文字） |
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | 入力テキスト |
| kana | string | yes | ひらがな/カタカナ変換結果 |
| output | string | yes | 出力形式（hiragana または katakana） |
| source | string | yes | 変換エンジン |
No examples provided.
torify_law.search Japan Law Search [Torify namespace — official] ~130
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]
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 取得件数（1-50、既定: 10） |
| title | string | yes | 法令タイトル（部分一致、例: 労働基準法） |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | 取得件数 |
| laws | array | yes | 法令一覧 |
| source | string | yes | データソース |
| total | number | yes | 総ヒット件数 |
No examples provided.
torify_name.romanize Japanese Name Romanizer [Torify namespace — official] ~208
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]
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Japanese name in katakana or hiragana. Kanji input is returned as-is (not converted). Add space between family and given name to split parts. / カタカナ必須・漢字入力時は変換されません。姓名の間にスペースを入れると姓/名を分離して変換 |
| order | string | – | family-first: family name first / 姓名順（既定）, given-first: given name first / 名姓順 |
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | 入力値 |
| order | string | – | 適用した名前順序 |
| parts | object | – | 姓名に分離できた場合の各パーツ |
| romaji | string | yes | ローマ字変換結果（例: SUZUKI ICHIRO） |
No examples provided.
torify_postal.lookup Japanese Postal Code Lookup [Torify namespace — official] ~118
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]
| Name | Type | Req | Description |
|---|---|---|---|
| zipcode | string | yes | 郵便番号（7桁、ハイフン任意。例: 1000005 または 100-0005） |
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | yes | Prefecture name / 都道府県名 |
| address2 | string | yes | City/ward/town name / 市区町村名 |
| address3 | string | yes | District/neighborhood name / 町域名 |
| cityEn | – | – | City/ward name in English (romanized) / 市区町村名（英語・ローマ字） |
| kana1 | string | yes | Prefecture name in katakana / 都道府県名（カタカナ） |
| kana2 | string | yes | City/ward/town name in katakana / 市区町村名（カタカナ） |
| kana3 | string | yes | District name in katakana / 町域名（カタカナ） |
| prefcode | string | yes | Prefecture code / 都道府県コード |
| prefectureEn | – | – | Prefecture name in English (e.g. Tokyo) / 都道府県名（英語） |
| townEn | – | – | District name in English (romanized) / 町域名（英語・ローマ字） |
| zipcode | string | yes | Postal code (7 digits) / 郵便番号（7桁） |
No examples provided.
torify_wareki.convert Japanese Era Date Converter [Torify namespace — official] ~288
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]
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Gregorian date YYYY-MM-DD, required when direction=g2w / 西暦日付（direction=g2w 時必須） |
| day | integer | – | Day 1-31 / 日（1〜31） |
| direction | string | yes | g2w: Gregorian to wareki / 西暦→和暦, w2g: wareki to Gregorian / 和暦→西暦 |
| era | string | – | Era name (Reiwa/Heisei/Showa/Taisho/Meiji or 令和/平成/昭和/大正/明治) |
| eraYear | integer | – | Era year (1 or greater) / 元号年（1以上） |
| month | integer | – | Month 1-12 / 月（1〜12） |
| Name | Type | Req | Description |
|---|---|---|---|
| day | number | – | 日（w2g 時） |
| era | string | – | 元号（例: 令和） |
| eraRomaji | string | – | 元号ローマ字（例: Reiwa） |
| eraYear | number | – | 元号年 |
| eraYearLabel | string | – | 元号年ラベル（例: 元年） |
| formatted | string | – | フォーマット済み日付文字列 |
| month | number | – | 月（w2g 時） |
| year | number | – | 西暦年（w2g 時） |
No examples provided.
wareki.convert Japanese Era Date Converter ~278
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.**
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Gregorian date YYYY-MM-DD, required when direction=g2w / 西暦日付（direction=g2w 時必須） |
| day | integer | – | Day 1-31 / 日（1〜31） |
| direction | string | yes | g2w: Gregorian to wareki / 西暦→和暦, w2g: wareki to Gregorian / 和暦→西暦 |
| era | string | – | Era name (Reiwa/Heisei/Showa/Taisho/Meiji or 令和/平成/昭和/大正/明治) |
| eraYear | integer | – | Era year (1 or greater) / 元号年（1以上） |
| month | integer | – | Month 1-12 / 月（1〜12） |
| Name | Type | Req | Description |
|---|---|---|---|
| day | number | – | 日（w2g 時） |
| era | string | – | 元号（例: 令和） |
| eraRomaji | string | – | 元号ローマ字（例: Reiwa） |
| eraYear | number | – | 元号年 |
| eraYearLabel | string | – | 元号年ラベル（例: 元年） |
| formatted | string | – | フォーマット済み日付文字列 |
| month | number | – | 月（w2g 時） |
| year | number | – | 西暦年（w2g 時） |
No examples provided.
How do I install the Torify — Japan Locale APIs for AI Agents MCP server?
Torify — Japan Locale APIs for AI Agents is a hosted endpoint at https://torify-mcp.torify.workers.dev/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · torify-mcp.torify.workers.dev
claude mcp add --transport http dev-torify-japanese-locale-mcp 'https://torify-mcp.torify.workers.dev/'
What is the Torify — Japan Locale APIs for AI Agents MCP server?
Torify — Japan Locale APIs for AI Agents is an MCP server listed in the public MCP registry as dev.torify/japanese-locale-mcp. 39 Japanese locale APIs, wareki, NTA invoice, 法人番号, postal, romanization, kanji-kana (Workers AI). This page covers its hosted endpoint (https://torify-mcp.torify.workers.dev).
Is the Torify — Japan Locale APIs for AI Agents MCP server safe to use?
Torify — Japan Locale APIs for AI Agents scores 18 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 Torify — Japan Locale APIs for AI Agents MCP server expose?
Torify — Japan Locale APIs for AI Agents exposes 24 tools: wareki.convert, torify_wareki.convert, invoice.validate, torify_invoice.validate, houjin.lookup, and 19 more. Their descriptions and schemas cost roughly 3,643 tokens of context every time the server is loaded.
Does the Torify — Japan Locale APIs for AI Agents MCP server require authentication?
Its publisher declares no required credentials for Torify — Japan Locale APIs for AI Agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Torify — Japan Locale APIs for AI Agents MCP server still maintained?
Torify — Japan Locale APIs for AI Agents is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.