39 Japanese locale APIs — wareki, NTA invoice, 法人番号, postal, romanization, kanji-kana (Workers AI).
AI & Agentsv0.2.0streamable-httptorify-mcp.torify.workers.dev repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 562ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo torify@0.2.0 |
| tooling | 35 / 35 | tools/list OK: 24 tools e.g. "wareki.convert"; 24/24 described, 24/24 fully-typed schemas, median description 306 chars |
| latency | 7 / 10 | initialize round-trip 562ms |
| provenance | 8 / 15 | description present; repository linked; version 0.2.0; namespace dev.torify does NOT match remote host (expected *.torify.dev) |
Score 90/100 · latency 562ms · 24 tools · auth: open
Claude Code:
claude mcp add --transport http japanese-locale-mcp https://torify-mcp.torify.workers.dev
Generic MCP client config:
{ "mcpServers": { "japanese-locale-mcp": { "type": "http", "url": "https://torify-mcp.torify.workers.dev" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/dev.torify/japanese-locale-mcp · referral link https://mcpqueen.com/go/dev.torify/japanese-locale-mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/dev.torify/japanese-locale-mcp)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 11:00 | A | 90 | 562ms |