get_office_action_rejections

Pack: uspto-office-actions · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/get_office_action_rejections for the schema, then POST the same URL with its arguments for the data.

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

Parameters

NameTypeRequiredDescription
application_numberstringyesUS patent application number, digits only or formatted.
limitnumbernoMax 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.
_apiKeystringnoUSPTO ODP API key. Get free at https://data.uspto.gov/myodp.

Example call

Arguments

{
  "application_number": "12190351",
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/uspto-office-actions/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_office_action_rejections","arguments":{"application_number":"12190351","limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('get_office_action_rejections', {
  "application_number": "12190351",
  "limit": 5
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the uspto-office-actions pack
{
  "mcpServers": {
    "uspto-office-actions": {
      "url": "https://gateway.pipeworx.io/uspto-office-actions/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 18, 2026