Skip to main content
Glama
dqj1998

Japan Company Info — MCP Server (Free Edition)

by dqj1998
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Japan Company Info — MCP Server (Free Edition)

No user-submitted related servers found.

    Related Servers

    • EDINET DB MCP Server

      edinetdb
      A
      license
      A
      quality
      C
      maintenance
      Structured financial data for ~3,800 Japanese listed companies from EDINET regulatory filings — financials, major shareholders, segments, executive compensation, and corporate history. Remote MCP over HTTPS with OAuth 2.0, free tier.
      13
      1
      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.
      -

    • tdnet-disclosure-mcp

      ajtgjmdjp
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Japan's TDnet (Timely Disclosure network). Search and retrieve timely disclosure documents from listed companies on Japanese stock exchanges.
      5
      Apache 2.0

    • edinet-mcp

      reanimatedead
      A
      license
      A
      quality
      B
      maintenance
      Lets AI assistants query normalized financial statements (P/L, B/S, C/F) of 3,634 Japanese listed companies from official EDINET filings, unified across J-GAAP, IFRS, and US GAAP with English keys. Zero setup: npx -y edinet-mcp.
      4
      6 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.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are entirely distinct: get_web_ui_url retrieves a local UI address while search_knowledge queries a knowledge base. There is no overlap and an agent can easily choose between them.

    Naming Consistency5/5

    Both names use a consistent snake_case verb_noun pattern (get_web_ui_url, search_knowledge). The convention is predictable and readable across the set.

    Tool Count3/5

    Two tools is thin for a company-information server; get_web_ui_url is incidental infrastructure rather than a domain capability. It is borderline rather than clearly mismatched.

    Completeness2/5

    The domain implies retrieving Japanese company details, but only a generic knowledge-base search is offered with no structured lookup, listing, or field-specific retrieval. Agents will hit dead ends for anything beyond free-text queries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources