KPIC MCP Server
Related Servers
Alternatives to KPIC MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables LLM agents to query Korean drug, DUR safety rules, and health supplement databases via MCP protocol.4MIT
- FlicenseNot gradedqualityCmaintenanceEnables users to understand lab test results, check food-drug interactions, and get medication information from official Korean sources. Offers personalized insights based on user's health profile and current medications.-
- AlicenseAqualityCmaintenanceEnables conversational drug and supplement lookup, detailed profiles, and interaction checking via the MedData API.7MIT
- AlicenseAqualityDmaintenanceEnables natural language querying of Korean public medical data (data.go.kr) through MCP clients like Claude, providing tools for searching hospitals, drugs, non-payment costs, disease statistics, and more.102MIT
- AlicenseBqualityDmaintenanceProvides access to the official FDA DailyMed database for comprehensive drug information, including drug labels, NDC codes, RxNorm mappings, pharmacologic classifications, and FDA application numbers through natural language queries.283MIT
- AlicenseNot gradedqualityDmaintenanceEnables drug safety, interactions, adverse events, and regulatory data queries using free sources like DrugBank, WHO, FDA FAERS, and more. Provides tools for checking drugs, interactions, adverse events, and searching across pharmaceutical databases.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: search_drugs_by_name retrieves preliminary information by drug name, while get_drug_detail_by_id fetches detailed information by drug code. Their descriptions explicitly reference each other to clarify when to use which, eliminating any ambiguity.
Both tools follow a consistent verb_noun pattern (search_drugs_by_name and get_drug_detail_by_id), using snake_case and descriptive names that clearly indicate their functions and parameters. There are no deviations in naming style.
With only 2 tools, the server feels under-scoped for a drug information domain. While the tools cover basic search and detail retrieval, typical drug information systems might include additional operations like filtering by category, checking interactions, or updating data, making this set appear thin and limited.
The tool set is severely incomplete for a drug information server. It lacks essential operations such as creating, updating, or deleting drug records, and does not cover common needs like drug interactions, dosage guidelines, or category-based searches. This will likely cause agent failures when more comprehensive tasks are required.