jp-ocr-date-fix
Related Servers
Alternatives to jp-ocr-date-fix
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to perform Japanese business calendar calculations including holiday detection, business day arithmetic, payment date settlement, and deadline management using local data.6MIT
- AlicenseAqualityDmaintenanceMCP server for Japanese business days, public holidays, wareki dates, and tax arithmetic, helping AI agents avoid common Japanese date and tax errors.7MIT
- AlicenseAqualityBmaintenanceEnables AI agents to verify that every number, money amount, percentage, count, date and time in an AI-written Japanese summary or meeting minutes actually appears in the source text, normalizing kanji numerals, 万/億, full-width digits, Japanese era years, 午前/午後 times and 割/分 rates before comparison. Exposes a read-only check tool that reports each fact as supported, approximate, mismatched or unsupported, plus an extraction tool that lists the quantities in a text.21MIT
- AlicenseNot gradedqualityDmaintenanceTorify gives AI agents the Japanese locale primitives that standard libraries lack — imperial era date conversion (wareki), qualified invoice number validation with NTA registry lookup, corporate number lookup (法人番号), postal code resolution, name romanization (Hepburn), and kanji-to-kana conversion via Yahoo! JLP. 31 endpoints total. No authentication required for MCP. Pay-per-call $0.02/call viaMIT
- AlicenseAqualityBmaintenanceExact date and time math for AI agents: business days with public holidays for 207 countries, DST-aware time-zone conversion, meeting-time overlap, cron schedules, RRULE expansion, SLA deadlines, payroll dates and natural-language date parsing. 13 tools. 25 free calls per day, then $0.001 per call via x402 (USDC on Base). No signup or API key.10241MIT
- AlicenseAqualityDmaintenanceJapan-specific utilities for AI agents — era ↔ Western year conversion, kanji-to-romaji, postal code lookup, national holidays, kana conversion, and Japanese name splitting. 9 tools, MIT licensed, install via uvx.929 PyPIMIT
TDQS
Scored across 2 tools
The two tools have related but distinguishable purposes: jp_ocr_fix_dates repairs dates in bulk text, while jp_ocr_check_date validates a single date string. There is some conceptual overlap because checking is a subset of fixing, but the descriptions make the batch-vs-single distinction fairly clear.
Both tools follow the same predictable pattern: a shared jp_ocr_ prefix followed by a verb_noun phrase (fix_dates, check_date). The convention is consistent and readable.
Two tools is a small surface, but the server has a narrow, well-defined purpose: repairing and checking Japanese OCR dates. The pair covers bulk and single-date use cases without obvious bloat, though it is on the thin side.
The surface covers the core workflow of finding/repairing dates and validating individual date strings, including edge cases like nonexistent calendar dates. Minor gaps exist, such as no dedicated pure-extraction or era-conversion tool, but these are not serious for the stated scope.