Korean Patent MCP
Related Servers
Alternatives to Korean Patent MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables searching and retrieving South Korean intellectual property data via the KIPRIS Plus Open API. Users can perform patent searches, look up bibliographic information, and convert natural language into KIPRIS search queries.62-
- AlicenseAqualityAmaintenanceEnables determining whether Korean patent applications/registrations are currently valid, verifying cited patent numbers in text, and searching Korean patents filtered by legal status, using KIPRIS Plus data.351 npm1MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to perform patent search, portfolio analysis, technology trend tracking, and semantic prior-art search using USPTO data.MIT
- AlicenseAqualityBmaintenanceMCP server that enables searching Korean patents, trademarks, and designs via KIPRIS Plus open APIs. Supports keyword, advanced, applicant, and rightholder searches with detailed bibliographic lookup.751 npm57MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to search and analyze Korean academic papers using the Korea Citation Index (KCI) Open API. Supports paper search, detailed metadata retrieval, reference analysis, author and keyword searches, and citation index queries.1-
- AlicenseNot gradedqualityBmaintenancePatent by Ouroboros Apps (https://ouroborosapps.com). USPTO patent search and prior art lookup: search public patent records, fetch a patent, list citations, and run a prior-art search. Not legal advice. USPTO only. Connect by pasting https://patent-mcp.vercel.app/mcp into Claude, Cursor, Grok, or ChatGPT developer mode (OAuth). Docs: https://ouroborosapps.com/docs/patentMIT
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.