Systematic medical reviews and evidence-based healthcare research
Free
Nothing to run from here
Patents is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
FastMCP TypeScript patent intelligence MCP server — 55 tools across USPTO, EPO, and BigQuery
Quickstart
# 1 — run it from where its publisher ships it
npx -y patents-mcp-server
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> FastMCP TypeScript patent intelligence MCP server — 55 tools across USPTO, EPO, and BigQuery
Publishernot claimed
SAAll 6 servers
sapientsai6 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Patents as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add patents-mcp -- npx -y patents-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
45 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Takes no parameters.
Example callreturns →
Get all patent family members by INPADOC family ID from Google Patents BigQuery. Returns all publications sharing the same family ID with country, title, dates. Complements epo-family-lookup with BigQuery
Takes no parameters.
Example callreturns →
Build a citation graph for a patent from Google Patents BigQuery. Returns all patents cited by the given patent (depth=1) or citations-of-citations (depth=2). Publication numbers in DOCDB format (e.g., US-7650331-B1). Useful for prior art analysis and understanding technology lineage.
Takes no parameters.
Example callreturns →
Patent filing statistics by CPC classification from Google Patents BigQuery. Returns patent counts, unique assignees, and date ranges for each CPC code matching the prefix. Useful for patent landscape analysis and identifying trends in technology areas.
Takes no parameters.
Example callreturns →
Get enriched citation data for a patent, including forward and backward citations with metadata about cited/citing patents.
Takes no parameters.
Example callreturns →
Search patent citations across the USPTO database.
Takes no parameters.
Example callreturns →
Get citation metrics for a patent including citation counts, citation velocity, and influence scores.
Takes no parameters.
Example callreturns →
Search patent litigation cases. Filter by plaintiff, defendant, patent number, court, and date range.
Takes no parameters.
Example callreturns →
Get detailed information about a specific patent litigation case.
Takes no parameters.
Example callreturns →
Get all litigation cases involving a specific patent.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get bibliographic data for a patent from EPO OPS. Returns title, applicants, inventors, classification, priority claims, and publication details.
Takes no parameters.
Example callreturns →
Get the abstract text of a patent from EPO OPS.
Takes no parameters.
Example callreturns →
Get the full claims text of a patent from EPO OPS. Use this for reading claim language when PPUBS is unavailable.
Takes no parameters.
Example callreturns →
Get the full patent description/specification text from EPO OPS. Use this for reading the detailed disclosure.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get worldwide legal status events for a patent from EPO OPS. Shows legal status across ~44 patent offices: granted, lapsed, opposed, withdrawn, etc. Critical for determining if a patent is still in force in specific jurisdictions.
Takes no parameters.
Example callreturns →
Convert a patent number between formats: docdb (CC.NNNNNNN.K), epodoc (CCNNNNNNN), and original filing format.
Takes no parameters.
Example callreturns →
Search USPTO patent applications via the Open Data Portal. Coverage: applications filed January 1, 2001 and later. Supports full-text search across application data.
Takes no parameters.
Example callreturns →
Get detailed information about a specific USPTO patent application by application number. Returns filing data, status, claims, and other application details.
Takes no parameters.
Example callreturns →
Get metadata for a USPTO patent application including application type, entity status, and dates.
Takes no parameters.
Example callreturns →
Get continuity data (parent/child relationships) for a patent application. Shows continuation, divisional, and CIP relationships.
Takes no parameters.
Example callreturns →
Get assignment/ownership records for a patent application. Shows current and historical assignees.
Takes no parameters.
Example callreturns →
Get patent term adjustment (PTA) data for an application. Shows delays attributable to the USPTO and applicant.
Takes no parameters.
Example callreturns →
Get attorney/agent information for a patent application.
Takes no parameters.
Example callreturns →
Get foreign priority claims for a patent application.
Takes no parameters.
Example callreturns →
Get transaction history for a patent application. Shows all prosecution events in chronological order.
Takes no parameters.
Example callreturns →
Get document listing for a patent application. Returns metadata about filed and issued documents.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Search USPTO bulk data datasets available through the Open Data Portal.
Takes no parameters.
Example callreturns →
Get details about a specific USPTO bulk data dataset by product ID.
Takes no parameters.
Example callreturns →
Get the full text of office actions for a patent application. Includes examiner rejections, objections, and requirements.
Takes no parameters.
Example callreturns →
Search office actions across USPTO patent applications.
Takes no parameters.
Example callreturns →
Get prior art citations from office actions for a patent application. Shows references cited by the examiner.
Takes no parameters.
Example callreturns →
Get rejection data from office actions for a patent application. Includes rejection types (35 USC 101, 102, 103, 112) and affected claims.
Takes no parameters.
Example callreturns →
Search PTAB (Patent Trial and Appeal Board) proceedings including IPR, PGR, and CBM trials. Returns trial metadata, parties, and status.
Takes no parameters.
Example callreturns →
Get detailed information about a specific PTAB proceeding by trial number.
Takes no parameters.
Example callreturns →
Get documents filed in a PTAB proceeding.
Takes no parameters.
Example callreturns →
Search PTAB decisions across all proceeding types.
Takes no parameters.
Example callreturns →
Get a specific PTAB decision by ID.
Takes no parameters.
Example callreturns →
Search ex parte appeals to the PTAB.
Takes no parameters.
Example callreturns →
Get details about a specific ex parte appeal.
Takes no parameters.
Example callreturns →
Check the health and configuration status of all patent data APIs (ODP, EPO, BigQuery).
Takes no parameters.
Example callreturns →
Look up CPC (Cooperative Patent Classification) code information. Returns the description for a given CPC section, class, or subclass code.
Takes no parameters.
Example callreturns →
Look up the meaning of a USPTO application status code. Returns a human-readable description of what the status code indicates about the application
Takes no parameters.
Example callreturns →
Startermost installed
$14 / month
- 11,000 calls a month, included
- 132 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Pro
$44 / month
- 60,000 calls a month, included
- 720 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Scale
$94 / month
- 280,000 calls a month, included
- 3,360 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $14 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 97 / 100
Release 1.0.4 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest847411adf0526b9e826796df465f9e51dc95c70fed6c7968dba7ee900e7a4506
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can send data / act on an external service
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest847411adf0526b9e
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.4 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.4
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Patents in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.