io.github.opendata-kr/narajangteo-corpinfo-mcp
OfficialRelated Servers
Alternatives to io.github.opendata-kr/narajangteo-corpinfo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceIntegrates 6 Korean public procurement APIs to search, analyze, and manage procurement data using natural language.83MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to query and analyze Korean public procurement data from the Korea Public Procurement Service (G2B/Nuri) via 14 services and 156 operations, including bid announcements, contracts, prices, and statistics.17-
- AlicenseNot gradedqualityCmaintenanceEnables searching Korean procurement notices from the public data portal, with support for integrated search across categories, flexible date ranges, and attachment extraction.MIT
- FlicenseNot gradedqualityBmaintenanceEnables searching and retrieving bid notices from the Korean Public Procurement Service (G2B) through Claude.-
- AlicenseAqualityBmaintenanceEnables users to search and analyze Korean public procurement IT bid announcements, including full bid opening results, through natural language conversation with Claude.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI to query real-time Korean public data including weather, real estate prices, air quality, economic indicators, and business registration via natural language.1MIT
TDQS
Scored across 2 tools
Each tool has a clearly distinct purpose: check_company_qualification verifies specific qualification criteria, while get_company_profile provides a full company overview. The descriptions explicitly cross-reference each other, eliminating ambiguity.
Both tool names follow the verb_noun pattern (check_company_qualification, get_company_profile), maintaining consistency in naming convention.
With only two tools, the server is minimal but reasonably scoped for its narrow domain of company information lookup. However, it feels slightly thin for broader use cases.
The server lacks any mechanism to look up companies by name or other identifiers; it requires a business registration number with no resolver. This is a significant gap that limits agent workflows.