Skip to main content
Glama
yamayued

j-platpat-mcp

by yamayued
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to j-platpat-mcp

No user-submitted related servers found.

    Related Servers

    • houjin-bangou-api-mcp

      yamayued
      A
      license
      B
      quality
      D
      maintenance
      MCP server for the Japan National Tax Agency Corporate Number API, enabling corporate number lookup and search via local AI clients.
      3
      1
      MIT

    • houan-mcp

      SHAYOUWORLD
      A
      license
      A
      quality
      C
      maintenance
      MCP server for searching Japanese Diet bills and committee Q\&A records via the NDL Kokkai API.
      4
      5 npm
      1
      MIT

    • e-gov-law-mcp

      kannkyo
      A
      license
      A
      quality
      A
      maintenance
      MCP server wrapping the e-Gov law API v2 to search and retrieve Japanese law data, including law lists, revision histories, full text, attachments, and keyword search.
      6
      2
      MIT

    • japan-corporate-mcp

      yamariki-hub
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for searching Japanese corporate data including companies, financials, patents, subsidies, and government statistics via official government APIs.
      1
      MIT

    • kaisha-mcp

      vladic-corp
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Kaisha API, providing official Japanese company-registry data including corporate numbers and qualified invoice registrations, with pay-per-call via USDC micropayments.
      2 npm
      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

    B3.1/5.0

    Scored across 27 tools

    Disambiguation4/5

    Tools are mostly separated by domain (patent/design/trademark) and resource type, making most purposes distinct. However, near-duplicate pairs like get_patent_progress vs get_patent_progress_simple and get_patent_family vs get_patent_family_list create some potential for misselection.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: get_*, resolve_*, and lookup_* with domain/resource prefixes. Minor noun abbreviations such as doc vs document and app_info are used consistently within families and do not break predictability.

    Tool Count2/5

    With 27 tools, the server exceeds the 25-tool threshold for 'too many' in the rubric. Although the breadth reflects three domains, the set is heavy and includes near-duplicate progress/simple variants that could be consolidated.

    Completeness4/5

    Core JPO retrieval operations across patents, designs, and trademarks are covered: registration, documents, progress, priority rights, citations, family, global/JP documents, and number resolution. Missing search/bulk discovery or some cross-domain utilities are minor gaps that agents can likely work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources