# Patent PreCheck (remote · patentprecheck.com)

Keyless 12-tool patentability MCP: USPTO pillar scores, prior art, hosted at patentprecheck.com/mcp.

- Trust score: 66/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `patentprecheck.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck.md), [page](https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck)
- npm · `@patentprecheck/mcp`: 63/100, [markdown](https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck-mcp.md), [page](https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck-mcp)

## Channel facts

- Endpoint: `https://patentprecheck.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1245 tokens (~103/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http patent-precheck-patent-precheck https://patentprecheck.com/mcp
```

### Codex

```toml
[mcp_servers.patent-precheck-patent-precheck]
url = "https://patentprecheck.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "patent-precheck-patent-precheck": {
      "type": "remote",
      "url": "https://patentprecheck.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add patent-precheck-patent-precheck --url https://patentprecheck.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  patent-precheck-patent-precheck:
    url: "https://patentprecheck.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "patent-precheck-patent-precheck": {
      "type": "http",
      "url": "https://patentprecheck.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (12)

### `precheck_score` (~169 tokens)

Patent PreCheck — score patentability

Run a patentability pre-check on source code or an invention description. Returns a 0–100 patentability score across the four USPTO statutory pillars (§101 eligibility, §102 novelty, §103 non-obviousness, §101 utility), a separate §112 filing-readiness signal, the band (Not Ready → File Ready), the pillar that holds the band back, top opportunities to strengthen, and a count of prior-art matches consulted. Pass the text to analyze inline via `code`.

Input parameters:

- `code` (string, required): The source code or invention description to analyze (>= 10 chars).
- `filename` (string): Optional filename hint (e.g. main.ts) used for language/context.
- `tier` (string): Analysis tier. Defaults to free; paid tiers require server-side entitlement.

### `precheck_prior_art` (~111 tokens)

Patent PreCheck — prior art matches

Return the closest prior-art matches consulted for an invention (titles, sources, similarity scores, URLs). Runs the same analyze pipeline as precheck_score but focuses on retrieval results. Pass invention text via `code`.

Input parameters:

- `code` (string, required): Source code or invention description (>= 10 chars).
- `filename` (string): Optional filename hint.
- `limit` (integer): Max matches to return (1–15, default 8).
- `tier` (string): Analysis tier. Defaults to free.

### `precheck_rejection_patterns` (~93 tokens)

Patent PreCheck — rejection pattern preview

Preview examination-risk signals: similar office-action rejections, abandonment patterns, and the primary statutory basis an examiner might cite (§101/§102/§103). Use after precheck_score to explain prosecution risk.

Input parameters:

- `code` (string, required): Source code or invention description (>= 10 chars).
- `filename` (string): Optional filename hint.
- `tier` (string): Analysis tier. Defaults to free.

### `precheck_legal_context` (~77 tokens)

Patent PreCheck — legal intelligence context

Return a short snippet of current US software-patent legal guidance (CAFC, USPTO, Alice/§101) relevant to scoring this invention. Informational only — not legal advice.

Input parameters:

- `code` (string, required): Source code or invention description (>= 10 chars).
- `filename` (string): Optional filename hint.

### `precheck_pillars` (~47 tokens)

Patent PreCheck — scoring reference

List the five patentability pillars (with statutes and weights) and the band rules used by precheck_score. Use this to explain a score to the user. No network call.

### `precheck_start_review` (~123 tokens)

Patent PreCheck — start an Interactive Code Review

Return the URL where the user can start a paid (or promo-unlocked) Interactive Code Review that strengthens each pillar with evidence and produces a filing package. Use after precheck_score when the user wants to act on the result.

Input parameters:

- `email` (string): Optional email hint (prefill only; user confirms on signup).
- `promo` (string): Optional promo / beta access code (e.g. Beta) to skip payment.
- `report_id` (string): Optional free-score report id (PPC-YYYY-MM-DD-XXXXX) to carry forward.

### `precheck_search_corpus` (~104 tokens)

Patent PreCheck — semantic corpus search

Fast semantic search against the 1M+ prior-art corpus without LLM scoring. Returns ranked matches with similarity scores. Cheaper than precheck_score when you only need references.

Input parameters:

- `code` (string, required): Source code or invention description (>= 10 chars).
- `filename` (string): Optional filename hint.
- `limit` (integer): Max matches (1–20, default 12).
- `tier` (string): Search tier. Defaults to free.

### `precheck_cpc_suggest` (~70 tokens)

Patent PreCheck — CPC classification hints

Suggest Cooperative Patent Classification (CPC) codes for an invention description. Offline heuristic — informational only. No network call.

Input parameters:

- `code` (string, required): Source code or invention description (>= 10 chars).
- `limit` (integer): Max suggestions (1–10, default 5).

### `precheck_session_status` (~70 tokens)

Patent PreCheck — ICR session status

Return status for an active Interactive Code Review session. Requires report_id and session_key from the user access email link.

Input parameters:

- `report_id` (string, required): Report id (PPC-YYYY-MM-DD-XXXXX).
- `session_key` (string, required): Session secret from the access email (?k=…).

### `precheck_deliverables` (~79 tokens)

Patent PreCheck — deliverable download links

Return download URLs for finalized ICR deliverables (filing packet, coaching report, package zip, scorecard PDF). Requires report_id and session_key.

Input parameters:

- `report_id` (string, required): Report id (PPC-YYYY-MM-DD-XXXXX).
- `session_key` (string, required): Session secret from the access email (?k=…).

### `precheck_lookup_patent` (~113 tokens)

Patent PreCheck — US patent lookup

Resolve a US patent or application number (e.g. US1234567B2) via USPTO Open Data Portal and optionally join the indexed prior-art corpus. Returns title, status, CPC, grant-text excerpt, and a public URL. No API key required in the MCP client.

Input parameters:

- `include_grant_text` (boolean): Fetch abstract / claim 1 excerpt when available (default true).
- `patent_id` (string, required): US patent id (US1234567B2) or application number.

### `precheck_compare_to_patent` (~97 tokens)

Patent PreCheck — compare invention to patent

Compare invention text to a known US patent: embedding similarity plus prior-art risk analysis (statute hints, overlap theme, distinction checklist). Use when the user names a specific reference patent.

Input parameters:

- `code` (string, required): Source code or invention description (>= 10 chars).
- `filename` (string): Optional filename hint.
- `patent_id` (string, required): US patent id (e.g. US1234567B2).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://patentprecheck.com/mcp
- Website: https://patentprecheck.com/integrations
- Changelog RSS feed: https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck/changelog.json
- HTML version of this page: https://verifymcp.io/servers/patent-precheck-patent-precheck/patentprecheck