Patent Search MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 74 installs a week from npm. Last commit 8 Jun 2026.
Patent dossiers, prosecution, claims + a legal layer (PTAB, litigation, term) + AI risk. USPTO.
What the code does
We read the source, 10 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
# Placeholder so the server starts. Real API keys come from users; this # value never reaches the AI Patent Search Generator backend (it'd fail # auth there anyway). ENV PATENT_SEARCH_API_KEY=placeholder-for-ci-validation
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add patent-search-mcp-server -e 'PATENT_SEARCH_API_KEY=<PATENT_SEARCH_API_KEY>' -- npx -y patent-search-mcp-server{
"mcpServers": {
"patent-search-mcp-server": {
"command": "npx",
"args": [
"-y",
"patent-search-mcp-server"
],
"env": {
"PATENT_SEARCH_API_KEY": "<PATENT_SEARCH_API_KEY>"
}
}
}
}[mcp_servers.patent-search-mcp-server]
command = "npx"
args = ["-y", "patent-search-mcp-server"]
env = { PATENT_SEARCH_API_KEY = "<PATENT_SEARCH_API_KEY>" }{
"mcpServers": {
"patent-search-mcp-server": {
"command": "npx",
"args": [
"-y",
"patent-search-mcp-server"
],
"env": {
"PATENT_SEARCH_API_KEY": "<PATENT_SEARCH_API_KEY>"
}
}
}
}{
"servers": {
"patent-search-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"patent-search-mcp-server"
],
"env": {
"PATENT_SEARCH_API_KEY": "<PATENT_SEARCH_API_KEY>"
}
}
}
}Put your own value in place of
<PATENT_SEARCH_API_KEY> (API key minted from the AI Patent Search Generator Chrome extension's Admin tab. Format: psg_live_... or psg_test_).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
PATENT_SEARCH_API_BASE (Override the API base URL. Default: https://us-central1-solicitation-matcher-extension.cloudfunctions.net/ai/v1).
Alternatives to Patent Search MCP Server
same job, measured the same waySearch patents & trademarks from EPO, USPTO & DPMA: claims, legal status, prosecution, PTAB
USPTO patent prosecution history: office action full text, examiner citations, claim-level…
The USPTO prosecution record for your AI. Connect once and work any U.S. patent application.
Dispatch litigation work to legal vendors from any MCP-compatible AI workflow. Patent pending.
US patent status for agents: applications, office actions, owners, PTAB, claims, monitors.
Dispatch litigation work to legal-services professionals from any MCP-compatible AI workflow.
US patents, applications and trademarks with full claims, owners, drawings and live USPTO records.
Runtime permission, approval, and audit layer for AI agent tool execution.
Patent Search MCP Server — questions
Answers built from our own checks of this server.