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
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to look up Korean businesses nationwide by region and industry, retrieve public-procurement vendor cards with contract records, and find open public bids from KONEPS, Defense e-Procurement, LH, K-water and Nuri-jangteo. It is read-only and requires no authentication, returning up to five results per tool call on the free tier.MIT
- 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.171-
- AlicenseNot gradedqualityBmaintenanceEnables users to search and inspect Korean public procurement data — bid notices, awards, pre-specifications, procurement plans, and contracts from Nara Market (G2B) and the Defense Electronic Procurement System (D2B) — directly inside Claude using their own Public Data Portal API key. It returns raw API values with sources, links each project from plan through contract, and offers setup checks for key and API approval status.MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants such as Claude, ChatGPT, and Cursor to search Korean public procurement bid announcements, view detailed bid information, access pre-specifications, and analyze award history from 나라장터 (Public Procurement Service), with source links and no installation or API key required for basic use.MIT
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.