# Uspto Office Actions (npm · @pipeworx/mcp-uspto-office-actions)

USPTO patent prosecution history: office action full text, examiner citations, claim-level…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 81/100, [markdown](https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/uspto-office-actions-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/uspto-office-actions-mcp)
- npm · `@pipeworx/mcp-uspto-office-actions`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/pipeworx-mcp-uspto-office-actions.md), [page](https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/pipeworx-mcp-uspto-office-actions)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-uspto-office-actions`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-uspto-office-actions).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add pipeworx-io-uspto-office-actions -- npx -y @pipeworx/mcp-uspto-office-actions
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-uspto-office-actions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-uspto-office-actions"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-uspto-office-actions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-uspto-office-actions"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-uspto-office-actions -- npx -y @pipeworx/mcp-uspto-office-actions
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-uspto-office-actions": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-uspto-office-actions"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-uspto-office-actions --command npx --arg -y --arg @pipeworx/mcp-uspto-office-actions
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-uspto-office-actions:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-uspto-office-actions"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-uspto-office-actions": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-uspto-office-actions"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-uspto-office-actions -t stdio -c npx -a -y @pipeworx/mcp-uspto-office-actions
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-uspto-office-actions": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-uspto-office-actions"
      ]
    }
  }
}
```

## 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-11-03 (score 81, +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.

### 2026-11-01 (score 80, +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-10-31 (score 79, +6)

- [security improvement] Source repository: unverified → pass

### 2026-10-30 (score 73, −5)

- [security regression] Provenance: pass → unverified

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (5)

### `search_office_actions` (~252 tokens)

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.

Input parameters:

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

### `get_office_action_text` (~232 tokens)

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.

Input parameters:

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

### `get_office_action_rejections` (~235 tokens)

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

Input parameters:

- `_apiKey` (string): USPTO ODP API key. Get free at https://data.uspto.gov/myodp.
- `application_number` (string, required): 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.

### `get_office_action_citations` (~229 tokens)

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.

Input parameters:

- `_apiKey` (string): USPTO ODP API key. Get free at https://data.uspto.gov/myodp.
- `application_number` (string, required): 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).

### `search_petition_decisions` (~287 tokens)

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.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/pipeworx-mcp-uspto-office-actions#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 73
- 2026-10-29: 78

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-uspto-office-actions
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-uspto-office-actions
- Repository: https://github.com/pipeworx-io/mcp-uspto-office-actions
- Website: https://pipeworx.io/packs/uspto-office-actions
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/pipeworx-mcp-uspto-office-actions.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/pipeworx-mcp-uspto-office-actions.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-uspto-office-actions/pipeworx-mcp-uspto-office-actions