Log inSubmit server
Patent Precheck MCP logo

Patent Precheck MCP

by Patent-PreCheck

Scores code for patentability across USPTO statutory pillars, prior-art signals, and filing readiness through CLI or MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Patent Precheck MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "patent-precheck-patent-precheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@patentprecheck/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Patent-PreCheck/patent-precheck-mcp MCP server connects AI coding agents to the hosted Patent PreCheck engine for code and invention patentability checks. It provides scores for §101, §102, §103, and §112-related filing readiness, along with prior-art and rejection-pattern signals. Run it locally through npx over stdio, or connect to the hosted Streamable HTTP endpoint without installing Node.js. Reach for it when you want an early, informational assessment before pursuing a patent filing, not a legal opinion.

Use cases

  • Score newly written code for early patentability signals
  • Check an invention description against statutory pillars
  • Search prior-art signals before discussing a filing
  • Gate CI when a score falls below a chosen threshold

Key features

  • USPTO pillar scoring
  • Prior-art and rejection-pattern tools
  • Filing-readiness signal
  • CLI and stdio MCP modes
  • Hosted Streamable HTTP endpoint
  • JSON output and CI thresholds

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @patentprecheck/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Patent Precheck MCP works

What Patent-PreCheck/patent-precheck-mcp does

Patent-PreCheck/patent-precheck-mcp evaluates source code or an invention description against patentability and filing-readiness indicators. Results cover the four statutory areas identified by the project: §101 eligibility, §102 novelty, §103 non-obviousness, and a separate §112 documentation or filing-readiness signal. The response includes an overall band ranging from Not Ready to File Ready, the pillar that limits the result, suggested areas to strengthen, and the amount of prior art consulted.

The assessment is intended as an informational pre-check. It is not legal advice and does not replace review by a licensed patent attorney. The hosted Patent PreCheck engine, scoring logic, and prior-art corpus remain on the service side, so the package does not require a user-supplied API key.

How it works

The package can run as a command-line program or as an MCP server. For local use, an MCP-compatible client starts npx -y @patentprecheck/mcp mcp, and the server communicates over stdio. A hosted Streamable HTTP option is available at https://patentprecheck.com/mcp; it accepts invention text inline and does not read local files.

Local CLI commands can score a file, read content from standard input, return JSON, display scoring references, or open the interactive review flow. A minimum score can also be used as a CI threshold, with a distinct exit code when the result falls below it. The local server is the appropriate option when an agent needs to provide a file path from the machine on which it runs.

Setup and configuration

Install on demand with npx -y @patentprecheck/mcp, or install the package globally with npm and use the precheck command. To expose MCP tools to a local client, configure the command with the mcp argument. Cursor can use the provided installation link or a .cursor/mcp.json entry, while Claude Code can add the server with its MCP command. The README also identifies Codex as a supported coding-agent context.

For a remote setup, configure the server URL as https://patentprecheck.com/mcp. This avoids a local Node.js installation but requires a client that supports Streamable HTTP MCP connections. No environment variables or API keys are documented as required.

Tools and capabilities

The MCP interface exposes 12 tools:

  • precheck_score for scoring supplied code or invention material
  • precheck_prior_art for prior-art signals
  • precheck_rejection_patterns for rejection-pattern information
  • precheck_legal_context for related legal context
  • precheck_pillars for the scoring reference
  • precheck_start_review for starting the review process
  • precheck_search_corpus for searching the available corpus
  • precheck_cpc_suggest for CPC suggestions
  • precheck_session_status for session information
  • precheck_deliverables for available deliverables
  • precheck_lookup_patent for patent lookup
  • precheck_compare_to_patent for comparison with a patent

The CLI supports human-readable and JSON output. It reads either a path or standard input, and its documented exit codes distinguish usage errors, request errors, a failed §101 gate, and results below a configured minimum score.

Limitations and notes

Patent-PreCheck/patent-precheck-mcp is designed for an early screening workflow rather than a definitive patentability determination. The hosted endpoint cannot inspect local files; pass the invention text inline or use the local stdio server when file access is needed.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Patent Precheck MCP

Patent-PreCheck/patent-precheck-mcp is an MCP server that connects AI coding agents to the hosted Patent PreCheck engine. Its main tools score code or invention text across USPTO statutory pillars, inspect prior-art signals, identify rejection patterns, provide legal context, and support patent lookup and comparison without requiring an API key.

Install it with `npx -y @patentprecheck/mcp`, then configure the MCP client to run `npx -y @patentprecheck/mcp mcp`. You can also install it globally with `npm i -g @patentprecheck/mcp` and use the `precheck` command.

Yes, it works with Cursor. Add the local stdio command to `.cursor/mcp.json`, use the repository's Add to Cursor link, or configure the hosted endpoint at `https://patentprecheck.com/mcp` for a remote connection.

Yes, the local CLI and stdio server can work with file paths. The hosted Streamable HTTP server does not read files from your machine, so provide invention text inline when using that endpoint.

Related MCP servers

All in Legal All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPatent Precheck MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/patent-precheck-patent-precheck-mcp?style=directory)](https://allmcps.com/mcp/patent-precheck-patent-precheck-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/patent-precheck-patent-precheck-mcp"><img src="https://allmcps.com/api/badge/patent-precheck-patent-precheck-mcp?style=directory" alt="Patent Precheck MCP on AllMCPs" /></a>