Skip to main content
Glama
hypn4

opendart-fss-mcp

by hypn4

Related Servers

Alternatives to opendart-fss-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Korea's DART (Data Analysis, Retrieval and Transfer) electronic disclosure system, operated by the Financial Supervisory Service (FSS). Exposes company disclosures, company profiles, and financial statements via the OpenDART public API.
      3
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that retrieves Korean stock fundamentals and financial data from OpenDART, enabling LLMs to access corporate disclosures, financial statements, and dividend information.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server that exposes seven read-only tools for querying Korean public company disclosures from the OpenDART system, returning normalized JSON.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP Server for public disclosure information of Korean companies, powered by the dartpoint.ai API.
      3
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Provides natural language access to South Korean corporate disclosure data, financial statements, and shareholder information through the DART Open API. It enables users to query 83 different tools for real-time reporting and regulatory filings from Korean listed companies.
      83
      21 PyPI
      3
      MIT

    TDQS

    C2.9/5.0

    Scored across 85 tools

    Disambiguation3/5

    Many tools are clearly separated by domain prefixes (financial_, report_, event_, etc.), but within groups there are overlapping concepts like report_director_compensation vs report_director_compensation_approval vs report_director_individual_compensation vs report_director_compensation_by_type, and event_asset_transfer vs event_business_acquisition vs event_business_disposal which could confuse an agent. The descriptions are terse and similar, making selection harder.

    Naming Consistency4/5

    The naming convention is largely consistent: domain prefix (financial_, report_, event_, disclosure_, registration_, shareholder_, utility_) followed by a descriptive noun phrase. However, there are minor inconsistencies such as 'financial_multi_account' vs 'financial_single_account' vs 'financial_single_indicators' and 'report_largest_shareholder_changes' vs 'report_largest_shareholders' which break the pattern slightly.

    Tool Count2/5

    85 tools is far beyond the typical well-scoped MCP server. While the domain (Korean financial disclosure) is broad, the tool count is excessive and will overwhelm agents. Many tools could be consolidated with parameters (e.g., a single event_decision tool with an event_type parameter).

    Completeness4/5

    The tool surface covers a wide range of financial disclosures: financial statements, XBRL, reports, events, registrations, and shareholder data. There are some minor gaps like no explicit tool for updating or deleting data, but for a read-only public disclosure API, the coverage is quite comprehensive. The inclusion of utility_get_current_date and disclosure_search_company helps agents navigate the API.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues