TRO Risk Detection MD
Product IP & Court Order Risk Check MCP
Screen product images for potential intellectual property risks, including temporary restraining orders (TROs). Call it via REST API or MCP.
Product IP & Court Order Risk Check 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. Screen Product IP And Court-Order Risks
Prompt: Screen [main product image] with [product title or description] for the IP and court-order risks supported by this tool. Return the report in [English or Chinese] and distinguish evidence from unverified risk signals.
2. Provide Comparison Evidence
Prompt: Screen [main product image] with [product title or description] for the IP and court-order risks supported by this tool. Return the report in [English or Chinese] and distinguish evidence from unverified risk signals. Include [up to three reference images], [up to five additional product images] and [up to three IP evidence images], with [comparison text] and [up to 20 IP keywords]. Keep each evidence source identifiable.
3. Prepare An IP Evidence Review Packet
Prompt: Screen [main product image] with [product title or description] for the IP and court-order risks supported by this tool. Return the report in [English or Chinese] and distinguish evidence from unverified risk signals. Include [up to three reference images], [up to five additional product images] and [up to three IP evidence images], with [comparison text] and [up to 20 IP keywords]. Keep each evidence source identifiable. Separate matched rights, owner and registration identifiers, risk descriptions and court-case references. Keep the returned risk scores as screening evidence and list unresolved issues for specialist review; do not declare infringement.
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_maidalv_product_tro_detectionhttps://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": "maidalv-product-tro-detection-1",
"method": "tools/call",
"params": {
"name": "nexscope_maidalv_product_tro_detection",
"arguments": {
"language": "zh",
"mainProductImage": "https://example.com/product.jpg"
}
}
}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 |
|---|---|---|---|
mainProductImage | string | required | Main product image as a public URL or data:image/...;base64, URI; maximum 1,000 characters. Example: https://example.com/product.jpg |
referenceImages | array | optional | Up to 3 reference images, each a public URL or image data URI. Example: [] |
otherProductImages | array | optional | Up to 5 additional product images, each a public URL or image data URI. Example: [] |
ipImages | array | optional | Up to 3 intellectual-property evidence images, each a public URL or image data URI. Example: [] |
referenceText | string | optional | Similar-product text, maximum 1,000 characters. Example: Wireless speaker |
description | string | optional | Product description, preferably the title; maximum 1,000 characters. Example: Portable wireless speaker |
ipKeywords | array | optional | Up to 20 intellectual-property keywords. Example: [
"speaker"
] |
language | string | optional | Legal report language: zh (default) or en; affects report only. Example: zh |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
errcode | integer | optional | Business status code, `200` indicates success |
errmsg | string | optional | Status description, `ok` when successful |
status | string | optional | Analyze the overall status, `success` when successful |
checkId | string | optional | The unique identifier for this test |
type | string | optional | Rendering style, such as `tableListWorkbenches` |
costToken | integer | optional | The token consumed by this call |
total | integer | optional | The number of high-risk infringement items, that is, the length of the `results` array |
riskLevel | string | optional | Overall risk assessment: `High Risk`, `Medium Risk` or `Low Risk` |
results | array | optional | List of high-risk potential infringement items, please see the "Infringement Item Fields" below for the fields. |
nonResults | array | optional | A list of IP items that are not high risk or low similarity, including information about possible TRO plaintiffs. See the "Infringement Item Fields" below for the fields. |
columns | array | optional | Rendered column definitions for display only; length may differ from data array |
ipType | string | optional | IP type: `Trademark`, `Copyright` or `Patent` |
text | string | optional | IP text content such as trademark text, patent title, or copyright title |
ipOwner | string | optional | Intellectual property right holder |
regNo | string | optional | Registration number, possibly an array of JSON strings, such as `["1221667"]` |
riskLevel | string | optional | Risk level: `High Risk`, `Medium Risk`, or `Low Risk`; does not appear if there is no rating |
riskScore | number | optional | 0-10 Numeric risk score; does not appear if there is no score |
riskDescription | string | optional | Risk level text description; does not appear if there is no score |
ipAssetUrls | string[] | optional | IP Evidence Image URL List |
plaintiffId | integer | optional | TRO Plaintiff ID, only appears if the IP appears in a TRO case |
plaintiffName | string | optional | TRO plaintiff name, appears only if the IP appears in a TRO case |
numberOfCases | integer | optional | Number of cases filed by this plaintiff; may be `null` if case details are not available |
lastCaseDocket | string | optional | Court docket number of the most recent case; may be `null` if case details are not available |
lastCaseDateFiled | string | optional | Date the most recent case was filed; may be `null` if case details are not available |
report | string | optional | AI-generated legal assessment report, the language is determined by the `language` parameter |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Screen [main product image] with [product title or description] for the IP and court-order risks supported by this tool. Return the report in [English or Chinese] and distinguish evidence from unverified risk signals.
Illustrative Response Explanation
The illustrative result contains no risk records. That absence is not proof of clearance; review the actual report and its evidence before making a decision.
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": "maidalv-product-tro-detection-example",
"method": "tools/call",
"params": {
"name": "nexscope_maidalv_product_tro_detection",
"arguments": {
"language": "zh",
"mainProductImage": "https://example.com/product.jpg"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "maidalv-product-tro-detection-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"total\":0,\"results\":[],\"nonResults\":[]}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"total": 0,
"results": [],
"nonResults": []
}
},
"isError": false
}
}