Patent Intelligence ZY
Patent Overview MCP
Look up patent titles, abstracts, dates, applicants, and inventors. Call the Patent Overview API via REST or MCP with your Nexscope API key.
Patent Overview 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. Read A Patent Overview
Prompt: Retrieve the core patent bibliography for publication [publication number]. Keep the patent identifier attached to the returned information and flag unavailable content.
2. Look Up A Known Patent ID
Prompt: Retrieve the core patent bibliography for [Nexscope patent ID]. Use that exact identifier and do not substitute a different patent silently.
3. Retrieve A Bounded Patent Batch
Prompt: Retrieve the core patent bibliography for [up to 100 publication numbers]. Keep each result associated with its input number and identify any missing records.
What You Need to Provide
Provide either a patent ID or a publication number. Where the contract states precedence, the patent ID takes priority if both are supplied.
Patent content and reported status are research evidence, not a legal opinion or confirmation of freedom to operate.
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_patent_core_bibliographyhttps://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": "patent-core-bibliography-1",
"method": "tools/call",
"params": {
"name": "nexscope_patent_core_bibliography",
"arguments": {
"patentNumber": "US10123456B2"
}
}
}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 |
|---|---|---|---|
patentId | string | optional | One or up to 100 Nexscope patent IDs separated by English commas; maximum 60,000 characters. Takes precedence when both identifiers are provided. Example: patent-id |
patentNumber | string | optional | One or up to 100 publication or grant numbers separated by English commas; maximum 60,000 characters. Example: US10123456B2 |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
total | integer | optional | Number of records. |
allRecordsCount | integer | optional | Total number of records. |
data | array | optional | List of bibliographic items. |
columns | array | optional | Rendered column definitions. |
type | string | optional | Rendering style. |
costToken | integer | optional | Consume token. |
patentId | string | optional | Patent ID. |
title | string | optional | Patent title. |
abstractContent | string | optional | Patent abstract. |
publicationNumber | string | optional | Public account. |
pn | string | optional | Public announcement number. |
country | string | optional | Country code. |
publicationCountry | string | optional | Open country. |
publicationDate | string | optional | Publication date. |
publicationKind | string | optional | Public type code. |
patentType | string | optional | Patent type (invention, utility model, design, etc.). |
kind | string | optional | Patent type code. |
applicationNo | string | optional | Application number. |
applicationDate | string | optional | Application date. |
applicants | array | optional | Applicant list. |
inventors | array | optional | List of inventors. |
assignees | array | optional | List of patent holders. |
assigneeAddresses | array | optional | List of patentee addresses. |
ipcMain | string | optional | IPC main classification number. |
ipcFurther | array | optional | List of IPC subclassification numbers. |
cpcMain | string | optional | CPC primary classification number. |
cpcFurther | array | optional | List of CPC subclassification codes. |
loc | array | optional | LOC List of classification numbers. |
gbc | array | optional | List of GBC classification numbers. |
priorityClaims | array | optional | Priority Statement List. |
pctApplicationNo | string | optional | PCT application number. |
pctFilingDate | string | optional | PCT filing date. |
pctEntryDate | string | optional | PCT entry date. |
citedPatents | array | optional | List of cited patents. |
citedNonPatents | array | optional | List of cited non-patent documents. |
Format Illustration
Illustrative example with fictional data, not a live tool call.
Illustrative Question
Retrieve the core patent bibliography for publication [publication number]. Keep the patent identifier attached to the returned information and flag unavailable content.
Illustrative Response Explanation
The illustrative response identifies US10123456B2 with the title “Example patent title” and country US. This demonstrates the record format without claiming a real bibliographic lookup.
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": "patent-core-bibliography-example",
"method": "tools/call",
"params": {
"name": "nexscope_patent_core_bibliography",
"arguments": {
"patentNumber": "US10123456B2"
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "patent-core-bibliography-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"total\":1,\"data\":[{\"pn\":\"US10123456B2\",\"title\":\"Example patent title\",\"country\":\"US\"}]}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"total": 1,
"data": [
{
"pn": "US10123456B2",
"title": "Example patent title",
"country": "US"
}
]
}
},
"isError": false
}
}