get_legal_status
Pack: epo-ops · 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_legal_status for the schema, then POST the same URL with its arguments for the data.
INPADOC legal status for a patent family, sourced from the EPO’s worldwide legal-status database — grant, lapse, opposition, withdrawal, appeal and renewal-fee events as reported by the national/regional offices that know about this filing. Answers “is this patent still in force” and “did it lapse for non-payment of a renewal fee”, which get_biblio, get_family and get_claims cannot. A European patent can stay in force in some contracting states while lapsing in others, so events are grouped per publication/country rather than collapsed into one in-force flag — read each member’s events to see which jurisdiction a given event applies to. Each event carries an influence of “negative” (lapse, withdrawal, refusal, revocation), “positive” (grant, renewal, fee paid) or “neutral” (procedural/informational). Give the publication number as printed on the document; a trailing kind code is handled for you. Requires _apiKey=consumer_key:consumer_secret.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
number | string | yes |
Example call
Arguments
{
"number": "EP2400812"
}
curl
curl -X POST https://gateway.pipeworx.io/epo-ops/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_legal_status","arguments":{"number":"EP2400812"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('get_legal_status', {
"number": "EP2400812"
});
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 epo-ops pack
{
"mcpServers": {
"epo-ops": {
"url": "https://gateway.pipeworx.io/epo-ops/mcp"
}
}
}
See Getting Started for client-specific install steps.