Korean Patent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIPRIS_API_KEY | Yes | Your KIPRIS Plus Open API key (obtain from https://plus.kipris.or.kr) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kipris_search_patentsB | 출원인명으로 한국 특허를 검색합니다. |
| kipris_get_patent_detailC | 출원번호로 특허의 상세 정보를 조회합니다. |
| kipris_get_citing_patentsC | 특정 특허를 인용한 후행 특허들을 조회합니다. |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: one retrieves patents citing a specific patent, another gets detailed information for a single patent, and the third searches patents by applicant name. The descriptions clearly differentiate these functions, making tool selection unambiguous for an agent.
All tool names follow a consistent 'kipris_verb_noun' pattern (kipris_get_citing_patents, kipris_get_patent_detail, kipris_search_patents). This uniform naming convention makes the tool set predictable and easy to understand, with no deviations in style or structure.
With only 3 tools, the set feels thin for a patent domain that typically involves more operations like updating, deleting, or analyzing patents. While the tools cover basic retrieval and search, the count is borderline low for comprehensive patent management, limiting agent capabilities.
The tool surface has significant gaps for a patent server, lacking essential operations such as creating, updating, or deleting patents, as well as advanced features like patent analysis or filtering by other criteria. This incompleteness will likely cause agent failures in handling full patent workflows.