Marka Patent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPSOLVER_API_KEY | Yes | API key for Capsolver, required to solve reCAPTCHA v3 protection on the TÜRKPATENT portal. |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_trademarksA | Search trademarks registered in Turkey on TURKPATENT. Returns a list of matching trademarks with application number, name, holder, status, Nice classes, and application date. Examples:
|
| get_trademark_detailsB | Get detailed information about a specific trademark application. Returns mark information including name, holder, Nice classes, application date, registration status, bulletin numbers, and protection dates. |
| search_patentsA | Search patents registered in Turkey on TURKPATENT. Returns matching patents with application number, title, applicant, IPC class, and publication date. Examples:
|
| get_patent_detailsA | Get detailed information about a specific patent application. Returns full patent information including title, abstract, inventors, applicant, IPC/CPC classes, priority claims, and publication dates. |
| search_designsA | Search industrial designs registered in Turkey on TURKPATENT. Returns matching designs with registration number, design name, applicant, Locarno class, and bulletin information. Examples:
|
| get_design_detailsA | Get detailed information about a specific design application. Use the fileId value from search_designs results to retrieve full details. Returns design information including design name, designer, applicant, Locarno class, registration details, and bulletin dates. |
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 6 tools
Each tool targets a distinct domain (trademark, patent, design) and action (search vs. detail retrieval), with no overlap in purpose. The boundaries are clear and an agent can easily select the right tool.
All tools follow a consistent verb_noun pattern: get_<singular>_details and search_<plural> across the three domains. There are no deviations or mixed conventions.
6 tools is well-scoped for a read-only search and detail retrieval service covering three IP domains. Each tool earns its place without redundancy.
The surface covers search and detailed retrieval for trademarks, patents, and designs, which is complete for a public data lookup service. No create/update/delete operations are expected in this context, and no obvious gaps exist.