patent_landscape
Search, analyze and map patent landscapes across major jurisdictions (US, EP, WO, CN, JP, KR). Three modes: (1) search — find patents by keywords, company name or inventor name; (2) landscape — aggregate distributions: top assignees, top inventors, CPC class breakdown, filings by year, citation l...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/patent-landscape.md
What patent_landscape does on Mcp Knowledge
AI agents call patent_landscape to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | search: keyword/inventor/assignee search; landscape: aggregate distributions; lookup: fetch by patent number. Default: "search" |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
query | string | Yes | Keywords, company/inventor name, or patent number (e.g. "machine learning", "Tesla Inc", "US10000000B2") |
date_to | string | — | ISO date YYYY-MM-DD — latest filing date |
date_from | string | — | ISO date YYYY-MM-DD — earliest filing date |
max_results | number | — | Max patents to return (5-50). Default: 20 |
jurisdictions | array | — | Jurisdictions to include. Default: ["US","EP","WO"] |
Parameters from the server's own tool schema.
Why patent_landscape is rated Low
patent_landscape is a read-only intelligence tool that queries patent databases (WIPO PatentScope, USPTO PatentsView, EPO OPS) and returns metadata, statistics, and patent documents. It retrieves and aggregates existing public patent information without creating, modifying, deleting, or executing operations. Risk is low because misuse yields only informational disclosure, not system compromise or data loss.
From the tool's definition Tool performs search, analyze, map, and lookup operations on patent data: 'Search, analyze and map patent landscapes', 'find patents by keywords, company name or inventor name', 'aggregate distributions', 'retrieve a specific patent by number'.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs patent_landscape safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For patent_landscape, this is the rule to start with:
patent_landscape is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every patent_landscape call is checked against it from then on.
Questions about patent_landscape
Search, analyze and map patent landscapes across major jurisdictions (US, EP, WO, CN, JP, KR). Three modes: (1) search — find patents by keywords, company name or inventor name; (2) landscape — aggregate distributions: top assignees, top inventors, CPC class breakdown, filings by year, citation leaders, white-space innovation opportunities; (3) lookup — retrieve a specific patent by number (e.g. US10000000B2, EP3456789A1, WO2023/123456). Primary source: WIPO PatentScope (WO PCT, keyless). Optional sources: USPTO PatentsView (US, env PATENTSVIEW_API_KEY), EPO OPS (EP/WO, env EPO_OPS_CONSUMER_KEY + EPO_OPS_CONSUMER_SECRET), Lens.org (global, env LENS_API_TOKEN). Use cases: freedom-to-operate (FTO) analysis, R&D gap identification, VC due diligence IP audit, competitor patent portfolio mapping, inventor network analysis. SLA: <=24s p95 (parallel fetches, 8s per source). Cache: 24h TTL (patent data stable). Quality score: 30 pts per retrieved source (max 90), +10 if >=10 patents, +10 bonus for landscape mode with non-empty top_assignees. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
patent_landscape accepts 7 parameters: mode, async, query, date_to, date_from, max_results, jurisdictions. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for patent_landscape: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Knowledge. Nothing to install.
patent_landscape is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the patent_landscape rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for patent_landscape. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
patent_landscape is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue