MCP.Market

Patent Maintenance Fees MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/patent-maintenance-fees·v0.2.1

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

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Patent Maintenance Fees yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Patent Maintenance Fees tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Patent Maintenance Fees compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
197 ms
faster than 64% of 30,031 servers

Release history: 3 versions in the registry since 2026-10-18, latest 2026-11-04, typically one every 12 days.

Install Patent Maintenance Fees in Claude Code, Cursor or VS Code

claude mcp add --transport http patent-maintenance-fees https://gateway.pipeworx.io/patent-maintenance-fees/mcp
Add to Cursor

What the publisher says

From the Patent Maintenance Fees repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/patent-maintenance-fees

Tell whether a US patent is still in force, or has lapsed for non-payment of maintenance fees — the one question the patents pack cannot answer, because its prosecution-event data has no fee field at all.

Part of Pipeworx — an MCP gateway connecting AI agents to 1831+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

maintenance-fee event for one patent (payments, surcharges, expiration for non-payment, reinstatement, entity-status changes), a computed status, and a 4th/8th/12th-year fee-window breakdown (due date, grace-period end, whether paid). Design (D-prefixed) and plant (PP-prefixed) patents are statutorily exempt from maintenance fees and report subjecttomaintenance_fees:false instead of a bare no-match.

  • getpatentmaintenancestatus(patentnumber) — every recorded

datefrom?, dateto?, limit?) — an exact totalmatching count first, then a capped, newest-first sample of the matching events. Useful for questions like "how many patents expired for non-payment last quarter" — pass eventcode: "EXP." and a date range.

  • searchmaintenancefeeevents(eventcode?, patentnumberprefix?,

Auth

Keyless.

Data source

USPTO, Patent Maintenance Fee Events — the Open Data Portal's bulk-data product recording every maintenance-fee event for US patents granted 1981-09-01 to present. US federal data, public domain.

Why this is a local-copy pack, not a live proxy

Checked first, per CLAUDE.md's local-copy rule: the ODP's Patent File Wrapper search/get-by-number API — the one mcps/patents already calls — returns prosecution events (eventDataBag: filing, publication, grant, office actions) but has no maintenance-fee field at all. Maintenance-fee history is published only as the "PTMNFEE2" bulk product, a single weekly-cumulative file, with no per-patent query endpoint. The legacy keyless host this product used to publish from (bulkdata.uspto.gov) no longer resolves in DNS as of 2026-10-17, confirmed against two independent public resolvers (NXDOMAIN/NODATA, not a transient block) — the product is reachable today only through ODP's own authenticated bulk-data API, which answers every /api/v1/ path 401/403 without an API key (the same credential type as the patents pack's PLATFORMUSPTO_KEY). A bulk file with no per-record API is exactly the case CLAUDE.md's sourcing rule calls for a refreshed backing store rather than a per-call upstream fetch.

This pack reads a Supabase mirror (usptomaintenancefeeevents, schema in supabase/migrations/260usptomaintenancefeeevents.sql), loaded by scripts/ingest-uspto-maintenance-fees.mjs (.github/workflows/uspto-maintenance-fees-refresh.yml, dispatch-only — see below). Every response carries dataasof from the mirror's own loadedat.

Not yet provisioned (as of the commit that added this pack)

Two things still need to happen before usptomaintenancefee_events has any rows, and both are outside what a commit-only build session can do:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Patent Maintenance Fees: common questions

Is Patent Maintenance Fees MCP server safe?
Mostly: it is graded B (77/100). Read the Patent Maintenance Fees safety report
How do I install Patent Maintenance Fees?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Patent Maintenance Fees need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Patent Maintenance Fees maintained?
The last commit was 17 days ago (2026-10-18). The latest release is v0.2.1.
Is Patent Maintenance Fees up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Patent Maintenance Fees compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 197 ms (faster than 64% of 30,031 servers). Full comparison.

More from pipeworx-io →