Patent Maintenance Fees
NPM · @PIPEWORX/MCP-PATENT-MAINTENANCE-FEES · 2 COMPONENTS
USPTO Patent Maintenance Fee Events — complements the `patents` pack (fleet #3258), which has…
Available components
Last scanned (2 hours ago)
Scores higher than 69% of npm servers
Category Education and Research
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-patent-maintenance-fees). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-patent-maintenance-fees@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-patent-maintenance-fees |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-patent-maintenance-fees/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685261128 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4f66e14f0aad3c139b9dc1480b54daec9c8940489a029fce4d0fe63b46cb03ce669b9399fbe2d356cba4b0562305955034d4ad2225779aa0bc5daef9b |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_patent_maintenance_status ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| patent_number | string | yes | US patent number, with or without commas, e.g. "10835610" or "10,835,610". Reissue numbers keep their "RE" prefix, e.g. "RE12345". |
No output schema declared.
No examples provided.
search_maintenance_fee_events ~257
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-patent-maintenance-fees
claude mcp add pipeworx-io-patent-maintenance-fees -- npx -y @pipeworx/mcp-patent-maintenance-fees
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.