Bridges Claude Code to the EPO Open Patent Services API v3.2. Provides 14 MCP tools for global patent search, retrieval, family/legal/register lookups, CPC classification, patent number conversion, enhanced quota monitoring, and rate-limit status.
14 tools with consistent naming (verb_noun pattern: ops_search_*, ops_retrieve_*, ops_check_*) and adequate descriptions (100-150 chars each). All tools are READ_ONLY, reducing risk. However, input schemas are inferred from the tool list rather than directly visible in source code, parameter type definitions, constraints, and output schemas are not shown. Descriptions lack actionable context (e.g., when to use ops_patent_family vs ops_patent_legal, what fields are returned, pagination behavior). No error handling guidance visible. Parameter descriptions are minimal (e.g., 'Patent number (e.g., EP2000000A1)' without format constraints or validation rules). Missing output schema documentation entirely.
Convert between different patent number formats (e.g., EP2000000A1 ↔ 2000000). Handles EP, US, WO, and other formats.
Retrieve CPC (Cooperative Patent Classification) information for a patent. Shows all CPC codes assigned to the patent.
Retrieve the patent family for a given patent number. Shows all related patents across different countries/regions.
Retrieve legal status information for a patent. Shows prosecution history, grants, renewals, and current legal status.
Retrieve register information for a patent. Shows current status, holder, and administrative details from the patent register.
Check current Fair Use quota status. Returns weekly remaining quota in GB, percentage used, and estimated reset time.
Output schemas not documented. No visibility into what fields are returned by ops_retrieve_patent, ops_patent_family, ops_patent_legal, etc. LLMs cannot plan downstream tool calls or extract required data without knowing response structure.
Parameter descriptions lack format constraints and validation rules. 'Patent number (e.g., EP2000000A1)' does not specify accepted formats, length limits, or regex patterns. LLMs cannot validate input before calling the tool.
No pagination guidance for search tools. ops_search_patents, ops_search_cpc, ops_search_applicant, ops_search_inventor accept 'range' parameter but no documentation of total count, next_cursor, or result limits. LLMs cannot handle large result sets.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | <=2025-11-25 | v2 |
Retrieve detailed information about a specific patent by number. Returns full bibliographic data, abstract, claims, and drawings metadata.
Search for patents by applicant name. Returns all patents filed by a specific applicant/assignee.
Search for patents by CPC classification code. Returns all patents assigned to a specific CPC class.
Search for patents by filing date range. Returns patents filed within the specified date range.
Search for patents by inventor name. Returns all patents invented by a specific person.
Search for patents using CQL (Common Query Language) or simple keyword queries. Returns paginated results with patent numbers, titles, and applicants.
Search for patents by publication date range. Returns patents published within the specified date range.
Check the last throttling/rate-limit status from the most recent OPS API call. Returns throttle headers and response details.
No error handling guidance. Source code shows 403 (Fair Use quota), 404 (not found), and generic 400+ errors, but tool descriptions do not explain recovery steps. LLMs cannot self-correct on quota exhaustion or invalid queries.
Tool definitions inferred from tool list, not directly visible in source. Input schemas (types, required fields, defaults) are not shown in the provided code snippet. Cannot verify schema completeness or parameter validation.