Skip to main content
Glama
japan-ai-tools

jp-ocr-date-fix

Related Servers

Alternatives to jp-ocr-date-fix

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform Japanese business calendar calculations including holiday detection, business day arithmetic, payment date settlement, and deadline management using local data.
      6
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Japanese business days, public holidays, wareki dates, and tax arithmetic, helping AI agents avoid common Japanese date and tax errors.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Torify 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 via
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Japan-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.
      9
      29 PyPI
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Verified locale data for AI agents: dates, phone numbers, currency formatting, VAT/sales-tax by date, public holidays, and addresses (UK & US). Returns checked answers and flags impossible inputs instead of guessing.
      7
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Exposes data validation as tools so an AI agent can check whether data is actually correct before using it, scoring CSV files with per-row problem details, catching impossible dates, inferring schemas, and generating readable reports.
      0
      MIT

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues