edinet-mcp
Related Servers
Alternatives to edinet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching for Japanese companies and retrieving their securities filings from Japan's Financial Services Agency, including daily filing lists and historical filing ranges for specific filers.157 npmMIT
- AlicenseAqualityBmaintenanceEnables interaction with the EDINET API v2 to handle disclosure documents such as annual securities reports, and supports building company-profile snapshots with key financial figures and peer comparisons.3MIT
- AlicenseAqualityCmaintenanceStructured 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.131MIT
- AlicenseBqualityDmaintenanceProvides comprehensive access to financial filings from 7,700+ Asian companies through Japan's EDINET and South Korea's DART systems, enabling search, retrieval, and analysis of financial statements, XBRL data, and dimensional breakdowns.13MIT
- AlicenseNot gradedqualityCmaintenanceProvides programmatic access to Japan's EDINET system to search for listed companies and retrieve annual or quarterly financial reports. It parses XBRL filings into structured data, enabling AI assistants to analyze balance sheets, income statements, and cash flows.182 PyPI20Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server for Japan's TDnet (Timely Disclosure network). Search and retrieve timely disclosure documents from listed companies on Japanese stock exchanges.178 PyPI6Apache 2.0
TDQS
Scored across 2 tools
The two tools are clearly distinct: list_filings discovers filings, while get_filing_document retrieves the actual PDF/CSV for a known ID. There is no overlap or risk of misselection.
Both tools follow a consistent snake_case verb_noun pattern (list_filings, get_filing_document). The convention is predictable and readable.
Two tools is on the thin side for a filing-data domain; discovery and retrieval are covered but remain a minimal surface. It is borderline rather than mismatched.
The core list-then-fetch workflow is covered, but there is no metadata lookup for a single filing, no search by company/ticker or date range, and no way to enumerate document types. Agents needing richer queries would hit dead ends.