# Patent Maintenance Fees (npm · @pipeworx/mcp-patent-maintenance-fees)

USPTO Patent Maintenance Fee Events — complements the `patents` pack (fleet #3258), which has…

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-patent-maintenance-fees`
- Version: `0.2.1`
- 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-patent-maintenance-fees).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 598 tokens (~299/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Patent Maintenance Fees MCP server?

Patent Maintenance Fees runs locally as an npm package, launched with npx -y @pipeworx/mcp-patent-maintenance-fees. 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-patent-maintenance-fees -- npx -y @pipeworx/mcp-patent-maintenance-fees
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-patent-maintenance-fees": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-patent-maintenance-fees"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-patent-maintenance-fees": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-patent-maintenance-fees"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-patent-maintenance-fees -- npx -y @pipeworx/mcp-patent-maintenance-fees
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-patent-maintenance-fees --command npx --arg -y --arg @pipeworx/mcp-patent-maintenance-fees
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-patent-maintenance-fees:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-patent-maintenance-fees"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-patent-maintenance-fees": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-patent-maintenance-fees"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-patent-maintenance-fees -t stdio -c npx -a -y @pipeworx/mcp-patent-maintenance-fees
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-patent-maintenance-fees": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-patent-maintenance-fees"
      ]
    }
  }
}
```

## 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-05 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 66, −12)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `get_patent_maintenance_status` (~281 tokens)

Look up a US patent's maintenance-fee history and in-force/expired status: every recorded maintenance-fee event (payments, surcharges, expiration for non-payment, reinstatement, entity-status changes) plus a computed status and a 4th/8th/12th-year fee-window breakdown (due date, grace-period end, whether paid). Give the patent number with or without commas ("10835610" or "10,835,610"). Design (D-prefixed) and plant (PP-prefixed) patents are statutorily exempt from maintenance fees and will report subject_to_maintenance_fees:false rather than a bare no-match. Sourced from USPTO's Patent Maintenance Fee Events (public domain, covers patents granted 1981-09-01 to present), refreshed from the weekly bulk file — every response carries data_as_of. Keyless. Does NOT determine full-term (20-year) expiration or any non-fee reason a patent could be invalid — this pack covers maintenance-fee lapses only; pair with the `patents` pack for prosecution history.

Input parameters:

- `patent_number` (string, required): US patent number, with or without commas, e.g. "10835610" or "10,835,610". Reissue numbers keep their "RE" prefix, e.g. "RE12345".

### `search_maintenance_fee_events` (~257 tokens)

Search USPTO maintenance-fee events across patents by event code, patent-number prefix, and/or event-date range — e.g. all 'EXP.' (expired for non-payment) events in a date window. Returns an exact total_matching count first, then a capped sample of the actual event rows (newest first) — never a bare empty array on zero matches; the filters tried are always echoed back. Sourced from USPTO's Patent Maintenance Fee Events (public domain); every response carries data_as_of. Keyless.

Input parameters:

- `date_from` (string): Event date lower bound, inclusive, YYYY-MM-DD.
- `date_to` (string): Event date upper bound, inclusive, YYYY-MM-DD.
- `event_code` (string): Exact USPTO event code, e.g. "EXP." (expired, non-payment), "EXPX" (reinstated), "M1551" (4th-year large-entity payment).
- `limit` (number): Max sample rows to return (default 50, max 200).
- `patent_number_prefix` (string): Patent-number prefix, e.g. "10835" or "RE4". Digits only unless a reissue "RE" prefix.

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 66
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78

## Common questions

### What is the Patent Maintenance Fees MCP server?

Patent Maintenance Fees is an MCP server listed in the public MCP registry as io.github.pipeworx-io/patent-maintenance-fees. USPTO Patent Maintenance Fee Events, complements the `patents` pack (fleet #3258), which has… This page covers its npm package (@pipeworx/mcp-patent-maintenance-fees).

### Is the Patent Maintenance Fees MCP server safe to use?

Patent Maintenance Fees 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 Patent Maintenance Fees MCP server expose?

Patent Maintenance Fees exposes 2 tools: get_patent_maintenance_status, search_maintenance_fee_events. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.

### Is the Patent Maintenance Fees MCP server still maintained?

Patent Maintenance Fees 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 Patent Maintenance Fees MCP server under?

Patent Maintenance Fees 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-patent-maintenance-fees
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-patent-maintenance-fees
- Repository: https://github.com/pipeworx-io/mcp-patent-maintenance-fees
- Website: https://pipeworx.io/packs/patent-maintenance-fees
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-patent-maintenance-fees/pipeworx-mcp-patent-maintenance-fees.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-patent-maintenance-fees/pipeworx-mcp-patent-maintenance-fees.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-patent-maintenance-fees/pipeworx-mcp-patent-maintenance-fees