opendart-fss-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENDART_API_KEY | Yes | OpenDART API key (required) | |
| OPENDART_MCP_HOST | No | HTTP bind address | 127.0.0.1 |
| OPENDART_MCP_PORT | No | HTTP port | 8000 |
| OPENDART_MCP_LOG_LEVEL | No | Log level: DEBUG | INFO | WARNING | ERROR | CRITICAL | INFO |
| OPENDART_MCP_TRANSPORT | No | Transport protocol: stdio | http | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 85 tools
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.
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.
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).
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.