j-platpat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JPO_BASE_URL | No | JPO API base URL | https://ip-data.jpo.go.jp |
| JPO_PASSWORD | Yes | Your JPO-issued password | |
| JPO_USERNAME | Yes | Your JPO-issued ID | |
| JPO_AUTH_PATH | No | JPO auth token endpoint path | /auth/token |
| JPO_USER_AGENT | No | User agent for API requests | j-platpat-mcp/0.1.0 |
| JPO_CACHE_TTL_MS | No | Cache TTL in milliseconds | 300000 |
| JPO_API_BASE_PATH | No | JPO API base path | /api |
| JPO_MIN_INTERVAL_MS | No | Minimum interval between requests in milliseconds | 250 |
| JPO_REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds | 30000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_number_relationC | Resolve official case number relationships from the JPO case number reference API. |
| get_patent_progressB | Fetch patent prosecution progress from the official JPO API. |
| get_patent_progress_simpleB | Fetch compact patent prosecution progress from the official JPO API. |
| get_patent_citationsC | Fetch cited document information for a patent application from the official JPO API. |
| get_patent_documentsC | Fetch patent application document bundles such as amendment, refusal reason, and decision packages. |
| get_patent_registrationB | Fetch patent registration information from the official JPO API. |
| get_patent_priority_right_app_infoC | Fetch patent priority-right information. |
| get_patent_divisional_app_infoC | Fetch patent divisional-application information. |
| get_patent_familyB | Fetch patent family record by case number. |
| get_patent_family_listC | Fetch patent family list by case number. |
| get_patent_global_cite_classC | Fetch patent global citation class information. |
| get_patent_global_doc_listC | Fetch patent global document list. |
| get_patent_global_documentC | Fetch one patent global document by document ID. |
| get_patent_jp_documentC | Fetch one patent Japan document by document ID. |
| get_patent_pct_national_phase_application_numberC | Resolve PCT national phase application number. |
| get_design_progressC | Fetch design prosecution progress from the official JPO API. |
| get_design_progress_simpleB | Fetch compact design prosecution progress from the official JPO API. |
| get_design_registrationB | Fetch design registration information from the official JPO API. |
| get_design_documentsB | Fetch design application document bundles such as amendment, refusal reason, and decision packages. |
| get_design_priority_right_app_infoC | Fetch design priority-right information. |
| get_trademark_progressC | Fetch trademark prosecution progress from the official JPO API. |
| get_trademark_progress_simpleB | Fetch compact trademark prosecution progress from the official JPO API. |
| get_trademark_registrationB | Fetch trademark registration information from the official JPO API. |
| get_trademark_documentsB | Fetch trademark application document bundles such as amendment, refusal reason, and decision packages. |
| get_trademark_priority_right_app_infoC | Fetch trademark priority-right information. |
| resolve_applicant_codeA | Resolve applicant code to name or name to applicant code using the official JPO applicant endpoints. |
| get_jplatpat_permalinkA | Resolve the official J-PlatPat fixed address for a patent, design, or trademark application. |
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 27 tools
Tools are mostly separated by domain (patent/design/trademark) and resource type, making most purposes distinct. However, near-duplicate pairs like get_patent_progress vs get_patent_progress_simple and get_patent_family vs get_patent_family_list create some potential for misselection.
All tools follow a consistent snake_case verb_noun pattern: get_*, resolve_*, and lookup_* with domain/resource prefixes. Minor noun abbreviations such as doc vs document and app_info are used consistently within families and do not break predictability.
With 27 tools, the server exceeds the 25-tool threshold for 'too many' in the rubric. Although the breadth reflects three domains, the set is heavy and includes near-duplicate progress/simple variants that could be consolidated.
Core JPO retrieval operations across patents, designs, and trademarks are covered: registration, documents, progress, priority rights, citations, family, global/JP documents, and number resolution. Missing search/bulk discovery or some cross-domain utilities are minor gaps that agents can likely work around.