# Patent-PreCheck/patent-precheck-mcp [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/Patent-PreCheck/patent-precheck-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1090  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/patent-precheck-patent-precheck-mcp

## Description
Patentability pre-check for code — USPTO statutory pillar scores (§101 eligibility, §102 novelty, §103 non-obviousness, §112 documentation), filing-readiness, and prior-art signals. No API keys; runs as a CLI or MCP server. Tools: precheckscore, precheckpillars, precheckstartreview. Install: npx -y @patentprecheck/mcp.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "patent-precheck-mcp": {
    "command": "npx",
    "args": ["-y","@patentprecheck/mcp"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/patent-precheck-patent-precheck-mcp/readme_