protogrid

Search / dev.torify/japanese-locale-mcp

Torify — Japan Locale APIs for AI Agents

not classified

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

v0.2.0 · active · repository · descriptor JSON · versions

Not classified yet.The remote endpoints have not been probed successfully, or the listing has nothing to connect to.
Quality85good
Trust56of 100
Uptime, 30 days38%
Latency p50678 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "japanese-locale-mcp": {
      "type": "http",
      "url": "https://torify-mcp.torify.workers.dev"
    }
  }
}
claude mcp add --transport http japanese-locale-mcp https://torify-mcp.torify.workers.dev
[mcp_servers.japanese-locale-mcp]
url = "https://torify-mcp.torify.workers.dev"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "japanese-locale-mcp": {
      "type": "remote",
      "url": "https://torify-mcp.torify.workers.dev",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "japanese-locale-mcp": {
      "type": "http",
      "url": "https://torify-mcp.torify.workers.dev"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=japanese-locale-mcp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdG9yaWZ5LW1jcC50b3JpZnkud29ya2Vycy5kZXYifQ%3D%3D"
}
{
  "servers": {
    "japanese-locale-mcp": {
      "type": "http",
      "url": "https://torify-mcp.torify.workers.dev"
    }
  }
}
{
  "mcpServers": {
    "japanese-locale-mcp": {
      "httpUrl": "https://torify-mcp.torify.workers.dev"
    }
  }
}
extensions:
  "japanese-locale-mcp":
    enabled: true
    name: "japanese-locale-mcp"
    type: streamable_http
    uri: "https://torify-mcp.torify.workers.dev"
    timeout: 300

Quality 85 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene86 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations24 of 24 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: torify_geo.geocode (destructiveHint); geo.reverseGeocode (destructiveHint); torify_geo.reverseGeocode (destructiveHint); …
  • pass
    tools.token_costabout 4,428 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

24 tools, about 4,428 tokens to load them all · tool set 5a3ef15423e2 · checked 2026-10-20 18:38 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 56 / 100

unreachable
provenance75
liveness0
freshness65
hygiene100

+repository +dns-namespace -unreachable(11 failures) ~updated-155d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://torify-mcp.torify.workers.dev streamable-httpnoneno (11 failures)38%678 ms2025-11-252026-09-25

Tools (24)

company.fullProfileread-onlyOne-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.
geo.geocoderead-onlyGeocode 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.**
geo.reverseGeocoderead-onlyReverse 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.**
houjin.lookupread-onlyLook 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.**
invoice.companyProfileread-onlyOne-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.
invoice.validateread-onlyValidate 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.**
invoice.verifyread-onlyVerify 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.**
kanji.toKanaread-onlyConvert 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.**
law.searchread-onlySearch 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.romanizeread-onlyHepburn 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.**
postal.lookupread-onlyJapanese 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_company.fullProfileread-onlyOne-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.geocoderead-onlyGeocode 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.reverseGeocoderead-onlyReverse 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.lookupread-onlyLook 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.companyProfileread-onlyOne-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.validateread-onlyValidate 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.verifyread-onlyVerify 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.toKanaread-onlyConvert 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.searchread-onlySearch 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.romanizeread-onlyHepburn 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.lookupread-onlyJapanese 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.convertread-onlyConvert 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]
wareki.convertread-onlyConvert 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.**

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "dev.torify/japanese-locale-mcp",
  "title": "Torify — Japan Locale APIs for AI Agents",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://torify-mcp.torify.workers.dev",
      "type": "streamable-http"
    }
  ],
  "version": "0.2.0",
  "repository": {
    "url": "https://github.com/endennn/torify-examples",
    "source": "github"
  },
  "description": "39 Japanese locale APIs — wareki, NTA invoice, 法人番号, postal, romanization, kanji-kana (Workers AI)."
}