Patent PreCheck
io.github.Patent-PreCheck/patent-precheck · v0.4.1
Keyless 12-tool patentability MCP: USPTO pillar scores, prior art, hosted at patentprecheck.com/mcp.
MCPremotelocal · npmno credentialsLaw & governmentDeveloper toolsAI & LLM
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 12 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 83/100
What it does: 12 tools · 0 read, 0 write · Developer tools, Law & government, AI & LLM
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://patentprecheck.com/mcpPackage
registry: npm
identifier: @patentprecheck/mcp
version: 0.4.1
transport: stdioTools
12 tools listed at last check
precheck_scoreRun 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 separate §112 filing-readiness signal, the band (Not Ready →precheck_prior_artReturn 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_patternsPreview 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_contextReturn 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_pillarsList 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_reviewReturn 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_corpusFast 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_suggestSuggest Cooperative Patent Classification (CPC) codes for an invention description. Offline heuristic — informational only. No network call.precheck_session_statusReturn status for an active Interactive Code Review session. Requires report_id and session_key from the user access email link.precheck_deliverablesReturn download URLs for finalized ICR deliverables (filing packet, coaching report, package zip, scorecard PDF). Requires report_id and session_key.precheck_lookup_patentResolve 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.precheck_compare_to_patentCompare 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.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.Patent-PreCheck/patent-precheck)