Check patent legal status and annuity events with AI with Patent Legal Status & Annuity, retrieving a consolidated procedural event timeline for a publication number.
This workflow works in Claude, Claude Code, ChatGPT, or Codex when the selected client supports the required MCP connection. After connecting, the research steps and evidence boundaries are the same.
When you need to verify whether a patent application has been granted, abandoned, or reached key examination milestones, the publication date alone doesn't tell the story. Patent registers record procedural events — filing acknowledgements, examination requests, publication triggers, fee deadlines — that determine current enforceability and prosecution status. An AI assistant or coding agent can interpret questions about legal timelines, but it can't access current patent-office registers or INPADOC legal-status records on its own — that's what Patent Legal Status & Annuity supplies, a server on Patsnap Open Platform — Patsnap's developer platform for connecting AI agents like Claude to patent, R&D, and life-sciences data through MCP servers, REST APIs, and UI widgets.
Why the event log uses codes instead of plain English
The event codes you'll see — PUAI, 17P, AK — aren't Patsnap's invention. They come from INPADOC's standardized legal-event code system, used consistently across patent offices worldwide so that a "request for examination" event looks the same whether it happened at the EPO, USPTO, or JPO. That standardization is what makes a cross-jurisdiction timeline possible at all — but it also means the raw log reads like shorthand until you know what each code stands for. An AI assistant or coding agent can translate the codes into plain language as it summarizes the timeline, but the underlying event log itself will always show the coded form.
Why this needs Patent Legal Status & Annuity
Official event data lives in jurisdiction-specific registers and the INPADOC legal-status file, not with AI's training corpus — a procedural event recorded recently, like a fee-payment acknowledgement, won't appear in any static snapshot. This server queries live Patsnap records that consolidate INPADOC and national-office filings into one event log across 12 tools — legal status, annuity, transfer, license, litigation, and reexamination data — so An AI assistant or coding agent can answer with the most recent procedural milestone and its official date, distinguishing active prosecution from abandonment.
Prepare your input
You need a patent publication number — that's what you'd already have from a prior search, a citation, or an FTO report. For this tutorial, the input is EP4721726A1, a European publication. If you're continuing a session where Claude already returned a Patsnap internal identifier from an earlier search, you can pass that instead; both resolve to the same record. But for a first-time lookup, the publication number is the realistic starting point.
Connect Patent Legal Status & Annuity
https://connect.patsnap.com/30096b/mcp?apikey=yourapikey
Replace yourapikey with your own Patsnap Open Platform API key before connecting. Keep the completed URL private.
- Claude: add the remote MCP connection from Claude's connector or integration settings.
- Claude Code: add the server as a remote HTTP MCP connection in your user or project configuration.
- ChatGPT: add the server through the supported connector or developer-mode MCP setup available to your workspace.
- Codex: add the server in Codex's MCP configuration for the relevant local workspace.
The interface differs by client, but you use the same Patsnap connection URL and the same natural-language research prompt.
- Get a Patsnap Open Platform API key.
- Copy the connection URL or JSON config from the Connect panel on the Patent Legal Status & Annuity page.
- Add the server to your AI assistant or coding agent or Cursor, then restart it.
- Confirm the legal status and annuity tools are available before you ask.
Run the example query
What is the legal status and event history for patent EP4721726A1?Claude calls legal_data(patent_number="EP4721726A1"), retrieving the INPADOC event log and any associated annuity or renewal records for that patent, returned as a structured timeline of milestones — each tagged with an event code, description, and official date.
Read the returned event log
| Code | Meaning | Date |
|---|---|---|
| PUAI | Art.153(3) EPC — Announcement in OJ of the application | 2026-03-06 |
| 17P | Request for examination filed | 2026-04-08 |
| AK | Designated contracting states listed | 2026-04-08 |
Each event is dated and described, so you can identify the current procedural stage and verify whether key milestones — examination request, publication, grant — have occurred. An AI assistant or coding agent can summarize this timeline in plain language and highlight the most recent event, but interpreting the legal significance of each code for your jurisdiction and business question is your call.
Go further with follow-up questions
- "Has this patent been granted, or is it still under examination?" — Claude checks the log for a grant code and summarizes the stage.
- "What's the most recent procedural event, and when did it occur?"
- "Are there annuity or renewal fee records for this patent?" — calls the fee_info tool if fee-related events exist.
- "What does the 17P code mean in this timeline?" — Claude explains any specific code inline.
Check patent legal status with AI
Connect Patent Legal Status & Annuity and pull a procedural event timeline for any publication number.
Frequently asked questions
Why can't I just Ask your AI assistant or coding agent for patent legal status directly?
the AI assistant or coding agent's training data does not include current patent-office registers or INPADOC legal-status records. Patent Legal Status & Annuity connects Claude to live Patsnap records that consolidate these events into a structured timeline.
What input do I need to check a patent's legal status?
A patent publication number, such as EP4721726A1. An internal Patsnap identifier from a prior search works too and resolves to the same record.
What information does the event log provide?
Procedural milestones such as filing acknowledgements, examination requests, publication events, and fee deadlines, each with an event code, description, and official date.
Can I rely on the event log for enforcement or licensing decisions?
The event log reflects Patsnap's records at the time of retrieval. Always confirm critical status questions against the official patent-office register before making enforcement or licensing decisions.
Can I use this workflow in Claude, Claude Code, ChatGPT, or Codex?
Yes, provided the selected client and workspace support the required MCP connection. Connect the same Patsnap server, then use the natural-language steps shown in this guide; interface details may differ by client.
Disclosure & disclaimer
Who published this
Published by Patsnap, which develops and sells the Patent Legal Status & Annuity MCP server described here. This is an editorial tutorial, not an independent review.
How the information was gathered
Server capabilities and connection details are taken from the Patent Legal Status & Annuity product page and Patsnap Open Platform documentation, as accessed on August 18, 2026. They are not the result of independent testing or benchmarking. Legal-event data and product capabilities change frequently and may have changed since publication.
Not legal advice
The event log in this tutorial is a records snapshot, not a legal opinion on enforceability or validity. Confirm any critical status question against the official patent-office register and consult a qualified patent professional before making an enforcement, licensing, or transaction decision.
Trademarks
All trademarks, service marks, product names, and company names mentioned — including Claude and Cursor — are the property of their respective owners and are used here solely for identification purposes. Their use does not imply any affiliation with, sponsorship by, or endorsement from their respective owners.