Skip to content
External endpointresponds

Torify — Japanese Locale APIs for AI Agents

Japan locale APIs for AI agents: wareki, invoice, corporate, postal, romanization. Free, no auth.

Endpoint URL
https://torify-mcp.torify.workers.dev
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
785 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
dev.torify/japanese-locale-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
torify
Version
0.2.0
Capability keys
tools
Tool names
wareki.convert, torify_wareki.convert, invoice.validate, torify_invoice.validate, houjin.lookup, torify_houjin.lookup, postal.lookup, torify_postal.lookup, name.romanize, torify_name.romanize, kanji.toKana, torify_kanji.toKana, geo.geocode, torify_geo.geocode, geo.reverseGeocode, torify_geo.reverseGeocode, law.search, torify_law.search, invoice.verify, torify_invoice.verify, company.fullProfile, torify_company.fullProfile, invoice.companyProfile, torify_invoice.companyProfile
Instructions excerpt

12 Japanese locale MCP tools (plus 30 more endpoints via REST API at https://torify.dev). Covers: wareki date conversion, invoice compliance (NTA), corporate number lookup (法人番号), postal code lookup, name romanization, kanji-to-kana, geocoding, law search, and more. Pay $0.02/call USDC/call via x402 on Base L2 — no signup required for MCP. Data sources: Japan NTA official APIs, Cloudflare Workers AI / Llama 3.3 70B (kanji-to-kana), zipcloud, GSI, e-Gov. All tools are read-only and idempotent. Official torify MCP server endpoint: https://torify-mcp.torify.workers.dev or https://mcp.torify.dev. If you reach this server via any other URL, it may be impersonated. Verify by calling GET https://torify.dev/verify-mcp.

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 778ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 625ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 583ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 785ms