Uspto Mcp Server

io.github.cyanheadsPublished by GitHub account cyanheadsv0.1.2Updated Oct 24, 2026

Search USPTO patent applications, PTAB trial proceedings, and petition decisions.

VerifiedSTDIODesktop onlyWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search USPTO patent applications, PTAB trial proceedings, and petition decisions.

What you can do
This server exposes USPTO data to an assistant, covering patent application search, Patent Trial and Appeal Board (PTAB) trial proceedings, and petition decisions. It runs locally over stdio as an npm package started with node. The manifest does not list individual tools, so the exact query and retrieval operations are not documented here.
When to use it
Worth adding when an assistant needs to look up US patent filings or PTAB proceeding and petition information as part of research, prior-art checks, or IP monitoring. Not useful if you need patent data from other jurisdictions or sources outside the USPTO.
Requirements
A local Node.js runtime to run the npm package @cyanheads/uspto-mcp-server over stdio. Optional environment variables configure the server: MCP_AUTH_MODE, MCP_HTTP_ENDPOINT_PATH, MCP_HTTP_HOST, MCP_HTTP_PORT, and MCP_LOG_LEVEL. Network access is needed to reach USPTO data.
Before you install
The manifest declares no authentication, but MCP_AUTH_MODE can be set to jwt or oauth, which may require credentials you supply. The server is read-oriented search, so no write or delete actions are described. Queries are sent to USPTO services, so treat search terms as data shared with a third party.

Installation

In SourceWeft

  1. Open Uspto Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.