docdb-mcp
This server resolves patent publication numbers to their canonical DOCDB (European Patent Office) identifiers. Specifically, you can:
Look up patent records by providing a two-letter country code (e.g.,
US,EP,WO) and a publication number (without kind code) to retrieve canonical DOCDB recordsNormalize DOCDB IDs — returns the canonical DOCDB ID including the kind code suffix (e.g.,
US8000000B2), useful for normalizing patents cited in varying formatsGet first inventor names (in caps) to verify matches against citations like "Greenberg et al."
Get publication dates (in
YYYYMMDDformat) to cross-reference patents cited with year referencesRetrieve patent family IDs to identify related patent documents across jurisdictions
Handle multiple document variants — if a publication number has both A1 and B2 versions, all matching records are returned so the correct one can be selected
Receive structured error guidance via error codes (e.g.,
cc_does_not_exist,number_is_not_alnum) to help correct malformed inputs
Note: Leading zeros in the number are ignored automatically; strip kind codes, hyphens, spaces, and slashes before calling. An empty result means no match was found, not an error.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@docdb-mcp resolve US patent 8,000,000 to DOCDB"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
docdb-mcp
An MCP server that resolves patent publication numbers to their canonical DOCDB identifiers.
What it does
Given a country code and publication number, resolve_docdb_id returns candidate
records with canonical DOCDB ID (including kind code), first inventor, publication
date, and family ID. This is useful for asserting that DOCDB identifiers are
correct, or for recovering properly normalized DOCDB identifiers from
citations that appear in different formats across documents:
US 8,000,000 (Greenberg)→US8000000B2
Related MCP server: mcp-fetch-patents
Installation
Option 1 — Hosted endpoint (no install)
A public MCP server is available at https://docdb.sarl-graip.fr/mcp using the
streamable HTTP transport. Configure your MCP client to point at it directly:
{
"mcpServers": {
"docdb": {
"type": "streamable-http",
"url": "https://docdb.sarl-graip.fr/mcp"
}
}
}No API key or credentials required.
Option 2 — Local install via uvx
Add this to your MCP client configuration (Claude Desktop, Continue, Cursor, etc.):
{
"mcpServers": {
"docdb": {
"command": "uvx",
"args": ["docdb-mcp"],
"env": {
"DOCDB_API_URL": "https://docdb.sarl-graip.fr"
}
}
}
}uvx installs and runs the package in one step — no virtualenv needed.
Tool reference
resolve_docdb_id(cc, number)
Parameter | Type | Description |
|
| Two-letter DOCDB country code, e.g. |
|
| Publication number without kind code, e.g. |
Strip the kind code before calling. The kind code is the trailing letter+digit suffix (B2, A1, A2, U1). Passing it returns an empty list, not an error.
"US8000000B2" → cc="US", number="8000000"
"EP1234567A1" → cc="EP", number="1234567"
"US 8,000,000" → cc="US", number="8000000"Returns a list of records (empty list = no match):
[
{
"docdb_id": "US8000000B2",
"inventor": "ROBERT J. GREENBERG",
"date_publ": "20110816",
"family_id": "39183031"
}
]Multiple records mean the same publication number has several document variants (e.g. an A1 and a B2 of the same application).
License
MIT
Available Tools
1 toolresolve_docdb_idA
Resolve a patent publication number to its canonical DOCDB record(s).
IMPORTANT — strip the kind code before calling: "US8000000B2" → cc="US", number="8000000" "EP1234567A1" → cc="EP", number="1234567" "WO2013143024" → cc="WO", number="2013143024" The kind code (trailing letter+digit suffix like B2, A1, A2, U1) is NEVER part of the number argument. Passing it causes an empty result, not an error.
Also strip formatting: "US 8,000,000" → cc="US", number="8000000".
Leading zeros in the number are ignored: "08000000" and "8000000" are equivalent.
Args: cc: Two-letter DOCDB country code, e.g. "US", "EP", "WO", "DE", "JP", "FR", "GB", "CN", "KR". Must be exactly 2 characters. number: Publication number without kind code or country prefix, digits and letters only (no hyphens, spaces, or slashes).
Returns: List of matching records, each with: - docdb_id: full DOCDB ID including kind code, e.g. "US8000000B2" - inventor: first inventor full name in caps, e.g. "ROBERT J. GREENBERG" - date_publ: publication date as YYYYMMDD, e.g. "20110816" - family_id: DOCDB patent family ID, e.g. "39183031" Multiple records mean the same publication number has several document variants (e.g. an A1 and a B2 publication of the same application). Empty list means no match — not an error.
If you get an empty list:
Check that you stripped the kind code (most common mistake).
Consider common transcription errors in the source material: O/0, I/1, S/5, B/8. Try plausible substitutions in the number.
Use all context available to you (inventor name, year) to reconstruct the most likely number and retry.
Processing the output: The tool returns the first inventor and publication date. These map directly onto the way patents are cited in practice: "Greenberg", "Greenberg et al.", or "Greenberg et al. (2011)" in a source document should match inventor "ROBERT J. GREENBERG" and date_publ starting with "2011". Use that correspondence to verify the match. If you get multiple records, compare inventor names and publication dates across the candidates to select the most likely one. In all cases you must decide: the tool gives you candidates, not a verdict.
Error codes returned by the server (not exceptions):
"cc_does_not_exist": cc is not a recognized DOCDB country code — check spelling or try the ISO 2-letter code for the country.
"number_is_not_alnum": number contains illegal characters such as hyphens, slashes, or spaces — strip them before retrying.
Inputs: cc (required), number (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion or ambiguity between tools.
The single tool name follows a clear verb_noun pattern (resolve_docdb_id) and is self-explanatory.
A single tool is minimal but can be appropriate for a very focused purpose like patent ID resolution. However, it feels thin for any broader use case.
The server covers only ID resolution, missing related operations like search, listing, or batch processing. For a narrow purpose it may be sufficient, but agents have no fallback if resolution fails.
Maintenance
Related MCP Connectors
Public patent search with ranked candidates, source links and coverage context. Developer beta.
Resolve DOI identifiers to Crossref titles, venues, dates and citation counts for reference checks.
US patent search, assignee portfolios, and citation graph via PatentsView.
EPO/USPTO search, citations, OCR, plus PATSTAT Portfolio Analytics, guarded SQL and Graph Analytics.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying patent data from the European Patent Office, including bibliographic info, patent families, abstracts, and claims.88 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables fetching patents from multiple global sources by patent ID, returning PDF, Markdown, and metadata with automatic caching.2Creative Commons Zero v1.0 Universal
- AlicenseNot gradedqualityBmaintenanceEnables searching and retrieving US patent records and published applications via keyword, assignee, inventor, or patent number, with full details such as claims, citations, and patent family.103 npmMIT
- AlicenseNot gradedqualityBmaintenanceFetches and normalizes public patent data from EPO OPS and Google Patents, providing search, bibliographic records, claims, legal status, and patent family information for prior-art exploration.Apache 2.0