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
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 |
|---|---|---|
cc |
str |
Two-letter DOCDB country code, e.g. "US", "EP", "WO" |
number |
str |
Publication number without kind code, e.g. "8000000" |
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
Metadata
Release files for docdb-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| docdb_mcp-0.1.2.tar.gz | 64.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docdb_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.1 kB
Release files / docdb_mcp-0.1.2.tar.gz
| Download URL | docdb_mcp-0.1.2.tar.gz |
|---|---|
| Size | 64.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa16e3be5f594c05b0c06785d2c4b5d88e54b9957b205ad9202b6c9d0c7eef9b
|
|
BLAKE2b-256 checksum How to use checksums |
4297d855cb61b620f74f5e4936b676a111dfd2dc04f331299e70096e3f34a785
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.20 {"installer":{"name":"uv","version":"0.9.20","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / docdb_mcp-0.1.2-py3-none-any.whl
| Download URL | docdb_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae0d5c05b18427db44e74c0eaf5fd0fa91c63304496d61de1f7466a7e5e2b2c2
|
|
BLAKE2b-256 checksum How to use checksums |
a762e8f6ad936a790a26aa334dd7d0f091043d4465138de26af2cb8a1eb4c2e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.20 {"installer":{"name":"uv","version":"0.9.20","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for docdb-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.