IP Risk Detection RG
Utility Patent Detector MCP
Search for similar utility and invention patents from product information. Call the Utility Patent Detector API via REST or MCP with your Nexscope API key.
Utility Patent Detector AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Find Potential Utility Patent Matches
Prompt: Search for utility-patent candidates for [product title] and [functional product description] in the US. Return [10 to 200] candidates for review; do not treat this as a freedom-to-operate opinion.
2. Prepare Patent Claim Candidates For Review
Prompt: Search for utility-patent candidates for [product title] and [functional product description] in the US. Return [10 to 200] candidates for review; do not treat this as a freedom-to-operate opinion. For the returned candidates, show claims, abstracts, applicants, publication numbers, validity labels and dates. Separate similarity ranking from claim analysis and do not declare freedom to operate.
3. Organize Patent Candidates By Applicant And Technology Class
Prompt: Search US utility-patent candidates for [product title] and [functional description], returning [10 to 200] results. Group the returned candidates by applicant and supplied classification codes, keeping publication identifiers and missing classes visible. Treat this as an index of the retrieved sample, not a complete patent landscape or proof that shared classes mean overlapping claims.
What You Need to Provide
Use returned matches and legal-status fields as research leads. They do not establish ownership, infringement, validity or freedom to operate. Dates and jurisdiction coverage must remain explicit.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_utility_patent_detectorhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "utility-patent-detector-1",
"method": "tools/call",
"params": {
"name": "nexscope_utility_patent_detector",
"arguments": {
"productDescription": "A protective smartphone case with a magnetic ring stand and shockproof corners.",
"productTitle": "Magnetic phone case with ring stand",
"region": "US",
"topNumber": 10
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
productTitle | string | required | Product title, max 1000 characters Example: Magnetic phone case with ring stand |
productDescription | string | required | Product description, max 1000 characters Example: A protective smartphone case with a magnetic ring stand and shockproof corners. |
region | string | required | Country/region code(s) where the product is intended for sale, multiple separated by commas. Currently supports US. Default US Example: US |
topNumber | integer | required | Number of results to recall, range: 10--200, default 100 Example: 10 |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
total | integer | optional | Number of records |
detectId | string | optional | Detection ID |
costToken | integer | optional | Consume token |
type | string | optional | Rendering style |
columns | array | optional | Rendered column definitions |
data | array | optional | Patent list (see patent object field below for details) |
globalUtilityId | string | optional | Patent ID |
title | string | optional | Invention patent title |
titleCn | string | optional | Invention Patent Title (Chinese) |
similarity | number | optional | How similar the product is to the patent (0-1) |
patentValidity | string | optional | Patent validity: `Active` (valid) or `Invalid` (invalid) |
applicationNumber | string | optional | Application number |
applicationDate | string | optional | Application date (yyyy-MM-dd) |
publicationNumber | string | optional | Public account |
publicationDate | string | optional | Open day (yyyy-MM-dd) |
estimatedDueDate | string | optional | Estimated maturity date (yyyy-MM-dd) |
region | string | optional | receiving office |
patentAbstract | string | optional | Summary |
patentAbstractCn | string | optional | Abstract (Chinese) |
claims | string | optional | claims |
claimsCn | string | optional | Claims (Chinese) |
specification | string | optional | Instructions |
specificationCn | string | optional | Instructions (Chinese) |
inventors | array | optional | Inventor and country splicing, array format |
inventorAddresses | array | optional | Inventor address, array format |
applicants | array | optional | Applicant and country concatenation, array format |
applicantAddresses | array | optional | Right holder address, array format |
priorityNumber | array | optional | Priority number, array format |
relatedPublicationDate | array | optional | First public date (yyyy-MM-dd), array format |
patentImageUrl | string | optional | Patent cover image |
images | array | optional | Patent drawings |
classNumList | array | optional | Category number path list, in the format of `classNum1 > classNum2 > classNum3` |
cpcKindRaw | array | optional | CPC classification (raw JSONArray) |
troCase | boolean | optional | Do you have a history of TRO rights protection? |
troHolder | boolean | optional | Is it the patent of the TRO right holder? |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Search for utility-patent candidates for [product title] and [functional product description] in the US. Return [10 to 200] candidates for review; do not treat this as a freedom-to-operate opinion.
Illustrative Response Explanation
The illustrative response contains no returned utility-patent candidates for this request. An empty result describes this example only; it does not establish complete database coverage or clearance for the product.
About this sample: Illustrative format example with fictional values, not a live tool call. Replace example inputs with your own permitted assets or public identifiers.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Illustrative example with fictional data, not a live tool call.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
{
"jsonrpc": "2.0",
"id": "utility-patent-detector-example",
"method": "tools/call",
"params": {
"name": "nexscope_utility_patent_detector",
"arguments": {
"productDescription": "A protective smartphone case with a magnetic ring stand and shockproof corners.",
"productTitle": "Magnetic phone case with ring stand",
"region": "US",
"topNumber": 10
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "utility-patent-detector-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"total\":0,\"data\":[]}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"total": 0,
"data": []
}
},
"isError": false
}
}