Skip to main content
Glama
kentaroajisaka

kigyounai-hoiku-mcp

by kentaroajisaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to kigyounai-hoiku-mcp

No user-submitted related servers found.

    Related Servers

    • labor-law-mcp

      kentaroajisaka
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Japanese labor and social insurance laws and administrative circulars from sources like the e-Gov API and the Ministry of Health, Labour and Welfare. It enables users to search for and retrieve legal texts and notices to ensure accuracy in labor-related inquiries.
      6
      1,437 npm
      61
      MIT

    • hailab-japan-company-data

      HOTAgithub
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server to search Japanese companies by corporate number or name and retrieve financial, subsidy, and procurement information from gBizINFO public data. Enables AI agents to query Japanese company data through natural language.
      -

    • Japan Data MCP

      yurukusa
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query Japanese public data (laws, corporations, statistics) from official government APIs, returning normalized English metadata with source attribution.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each search_* tool targets a distinct document corpus: supervision standards, implementation guidelines, unit-price tables, FAQ, notices, and audit documents. search_law and get_law are clearly split into discovery versus targeted retrieval, and the descriptions explicitly tell agents when to use search_tanka vs search_youkou.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case verb_noun pattern: seven are search_<corpus> and one is get_law. The single get_law is a natural counterpart to search_law and does not break the convention.

    Tool Count5/5

    8 tools is well within the ideal range for a domain-specific regulatory research server. Each tool maps to a meaningful document type or retrieval mode, so none feel redundant and none are missing.

    Completeness5/5

    The tool surface covers the full research workflow for this domain: searching laws, retrieving specific provisions, finding supervision standards, querying structured subsidy rates, and searching guidelines, FAQ, notices, and audit documents. There are no obvious dead ends for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources