Skip to content
Patent PreCheck logo

Patent PreCheck MCP server

Which servers in the official MCP registry are Patent PreCheck's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-09

← Back to Patent PreCheck

Whose server it is
  • Registry nameio.github.Patent-PreCheck/patent-precheckpublished by Patent-PreCheck on GitHub

Published under the GitHub organisation Patent-PreCheck, the same one patentprecheck.com links from its homepage. The registry ties that namespace to a GitHub sign-in.

When we asked itchecked 2026-10-09
  • Stateanswerschecked 2026-10-09
  • Tools12
  • Server calls itselfpatent-precheck
  • Server version0.4.3
  • Protocol version2025-06-18

On 2026-10-09 the server answered initialize and tools/list without a sign-in. First answer in 149 ms.

Tools it offers12 tools · read 2026-10-09
  • precheck_score

    Run a prior-art density / risk-profile pre-check on source code or an invention description. Returns a 0–100 directional score across the four USPTO statutory pillars (§101 eligibility, §102 novelty, §103 non-obviousness, §101 utility), a…

  • precheck_prior_art

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

  • precheck_rejection_patterns

    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.

  • precheck_legal_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.

  • precheck_pillars

    List the five scoring 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

    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.

  • precheck_search_corpus

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

  • precheck_cpc_suggest

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

  • precheck_session_status

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

  • precheck_deliverables

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

  • precheck_lookup_patent

    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…

  • precheck_compare_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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.