Uspto Office Actions
NPM · @PIPEWORX/MCP-USPTO-OFFICE-ACTIONS · 2 COMPONENTS
USPTO patent prosecution history: office action full text, examiner citations, claim-level…
Available components
Last scanned (3 hours ago)
Scores higher than 68% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-uspto-office-actions). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1291 tokens (~258/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +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.
- 31 Oct 26 +6
- Source repository: unverified → pass ▲ security
- 30 Oct 26 −5
- Provenance: pass → unverified ▼ security
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-uspto-office-actions@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-uspto-office-actions |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-uspto-office-actions/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560913581 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2c00e4c15c04253f4bd5dcd7c42de558e6bda56ddfaa7b7adf49b4ed6c501f28f92f45dfc97b8779214d30d4736a64a7cd43b9cdd2e5b5bfee391f4b7 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_office_action_citations ~229
References cited in office actions for one application — who cited each one (examiner vs applicant), the legal basis (102/103 etc.) it was cited under, and the AI/ML-extracted "enriched citation" fields (category code, claim/paragraph passage mapping) when USPTO has them for that citation. Returns `citations` (basic citation records) and `enriched_citations` (richer subset) separately rather than force-merged, since the two datasets are not joined by a shared key.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | USPTO ODP API key. Get free at https://data.uspto.gov/myodp. |
| application_number | string | yes | US patent application number, digits only or formatted. |
| include_raw | boolean | – | Debug escape hatch: skip normal parsing and return the bare upstream HTTP status + first 500 chars of body instead (fleet #3305 — diagnosing a request shape live, no redeploy needed). |
| limit | number | – | Max rows per array to return (default 25, max 100). |
No output schema declared.
No examples provided.
get_office_action_rejections ~235
Claim-level rejection data for every office action on one application. Returns AGGREGATE counts first (how many rejection records cite 35 U.S.C. 101/102/103/112, and double-patenting) and per-claim/per-record detail last. Use this before get_office_action_citations when the question is "what did the examiner reject this on", not "what references were cited".
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | USPTO ODP API key. Get free at https://data.uspto.gov/myodp. |
| application_number | string | yes | US patent application number, digits only or formatted. |
| include_raw | boolean | – | Debug escape hatch: skip normal parsing and return the bare upstream HTTP status + first 500 chars of body instead (fleet #3305 — diagnosing a request shape live, no redeploy needed). |
| limit | number | – | Max per-record rows to return in `records` (default 25, max 100). The `aggregate` block always covers every record USPTO returned for this application, not just `limit` of them. |
No output schema declared.
No examples provided.
get_office_action_text ~232
Fetch one USPTO office action's full text. Pass document_id (from search_office_actions' document_id field) for an exact match, or application_number + mail_date to look it up by application and date. Returns the office action body text, its character length, and a truncation flag.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | USPTO ODP API key. Get free at https://data.uspto.gov/myodp. |
| application_number | string | – | US patent application number — use with mail_date when you do not have a document_id. |
| document_id | string | – | The office action's document id, as returned by search_office_actions (field document_id). |
| include_raw | boolean | – | Debug escape hatch: skip normal parsing and return the bare upstream HTTP status + first 500 chars of body instead (fleet #3305 — diagnosing a request shape live, no redeploy needed). |
| mail_date | string | – | The office action mail date (ISO YYYY-MM-DD), from search_office_actions' mail_date field. Required when document_id is not given. |
No output schema declared.
No examples provided.
search_office_actions ~252
Search USPTO office actions (and related prosecution-history documents, e.g. petition decisions filed in the same document stream) for one patent application. Returns action type (non-final rejection, final rejection, notice of allowance, etc.), mail date, examiner employee number, and art unit — newest first. Use get_office_action_text with the returned document_id to fetch one office action's full text. Pass application_number (preferred) or patent_number.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | USPTO ODP API key. Get free at https://data.uspto.gov/myodp. Falls back to platform key if configured. |
| application_number | string | – | US patent application number, digits only or formatted, e.g. "16123456" or "16/123,456". |
| include_raw | boolean | – | Debug escape hatch: skip normal parsing and return the bare upstream HTTP status + first 500 chars of body instead (fleet #3305 — diagnosing a request shape live, no redeploy needed). |
| limit | number | – | Max rows to return (default 10, max 100). |
| patent_number | string | – | Granted US patent number, as an alternative to application_number. |
No output schema declared.
No examples provided.
search_petition_decisions ~287
Search USPTO Commissioner / Office of Petitions final decisions. Pass application_number for one application's petition history, or query for free-text search across decisions (petition issue text, invention title). Optional decided_after/decided_before (ISO YYYY-MM-DD) bound the decision date. Returns decision type, decision date, petition type, and the deciding office.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | USPTO ODP API key. Get free at https://data.uspto.gov/myodp. |
| application_number | string | – | Filter to one US patent application number. |
| decided_after | string | – | Only decisions on/after this date (ISO YYYY-MM-DD). |
| decided_before | string | – | Only decisions on/before this date (ISO YYYY-MM-DD). |
| include_raw | boolean | – | Debug escape hatch: skip normal parsing and return the bare upstream HTTP status + first 500 chars of body instead (fleet #3305 — diagnosing a request shape live, no redeploy needed). |
| limit | number | – | Max rows to return (default 10, max 100). |
| offset | number | – | Pagination offset (default 0). |
| query | string | – | Free-text search, e.g. an invention title fragment or petition issue (e.g. "revival", "extension of time"). Omit to list recent decisions, or combine with application_number. |
No output schema declared.
No examples provided.
How do I install the Uspto Office Actions MCP server?
Uspto Office Actions runs locally as an npm package, launched with npx -y @pipeworx/mcp-uspto-office-actions. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-uspto-office-actions
claude mcp add pipeworx-io-uspto-office-actions -- npx -y @pipeworx/mcp-uspto-office-actions
What is the Uspto Office Actions MCP server?
Uspto Office Actions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/uspto-office-actions. USPTO patent prosecution history: office action full text, examiner citations, claim-level… This page covers its npm package (@pipeworx/mcp-uspto-office-actions).
Is the Uspto Office Actions MCP server safe to use?
Uspto Office Actions scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Uspto Office Actions MCP server expose?
Uspto Office Actions exposes 5 tools: search_office_actions, get_office_action_text, get_office_action_rejections, get_office_action_citations, search_petition_decisions. Their descriptions and schemas cost roughly 1,235 tokens of context every time the server is loaded.
Is the Uspto Office Actions MCP server still maintained?
Uspto Office Actions is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Uspto Office Actions MCP server under?
Uspto Office Actions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.