get_patent_transactions
Pack: patents · 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_patent_transactions for the schema, then POST the same URL with its arguments for the data.
Fetch the full USPTO prosecution/transaction history for one patent application — every dated event the Office recorded against the case (filings, mailings, fee payments, office actions, notices, the grant itself), newest first. This is a superset of the handful of events get_patent surfaces: use this tool when the question is about the PROSECUTION HISTORY itself (how many office actions, when was it mailed, when did examination start) rather than just the current status.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
number | string | yes | US application number, digits only or formatted. Examples: “18926509”, “16/123,456”. |
limit | number | no | Maximum number of events to return, newest first (default 50). The full history is usually under 100 events; a note in the response says when more exist than were returned. |
_apiKey | string | no | USPTO ODP API key. Get free at https://data.uspto.gov/myodp. |
Example call
Arguments
{
"number": "17248024",
"limit": 5
}
curl
curl -X POST https://gateway.pipeworx.io/patents/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_patent_transactions","arguments":{"number":"17248024","limit":5}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('get_patent_transactions', {
"number": "17248024",
"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 patents pack
{
"mcpServers": {
"patents": {
"url": "https://gateway.pipeworx.io/patents/mcp"
}
}
}
See Getting Started for client-specific install steps.