Skip to main content

dcert (Python)

CI/CD Pipeline PyPI version License: MIT

A Python MCP wrapper for the dcert Rust server.

The package uses FastMCP to run a transparent proxy around the dcert-mcp Rust binary and exposes all TLS certificate tools over the Model Context Protocol. Tools added to the Rust binary are discovered at runtime, so the Python layer never needs to change.

Requirements

  • Python 3.12 or later
  • The dcert-mcp Rust binary. Platform wheels bundle it; the universal wheel downloads it on first use after verifying its SHA256 checksum.

Installation

pip install dcert

Platform wheels exist for Linux x86_64 (glibc 2.35 or later), macOS Intel, macOS Apple Silicon and Windows x86_64. The universal wheel works everywhere else that a release archive exists for.

Quick start

As a server

from dcert import create_server

create_server().run()  # stdio transport

As a client

import asyncio
from dcert import create_client

async def main() -> None:
    async with create_client() as client:
        tools = await client.list_tools()
        result = await client.call_tool("analyze_certificate", {"target": "example.com"})
        print(len(tools), result)

asyncio.run(main())

Typed async tool functions

The functional API opens a session (a subprocess plus its resilience stack) and passes it to plain async functions:

import asyncio
from dcert import analyze_certificate, check_expiry, create_session, export_pem

async def main() -> None:
    async with create_session(timeout=60.0) as session:
        cert = await analyze_certificate(target="example.com", session=session)
        expiry = await check_expiry(target="example.com", days=90, session=session)
        pem = await export_pem(target="example.com", output_path="chain.pem", session=session)
        raw = await session.call("tls_connection_info", {"target": "example.com"})

asyncio.run(main())

Leaving out session uses a shared default session that is created on first use and reused afterwards; close_default_session() shuts it down. The shared session belongs to the event loop that created it: a later asyncio.run() gets a fresh one, and calling close_default_session() before a loop ends releases the subprocess cleanly.

Function Description
analyze_certificate() Decode and analyse TLS certificates
check_expiry() Check certificate expiry within N days
check_revocation() Check OCSP revocation status
compare_certificates() Compare certificates between two targets
tls_connection_info() TLS connection details (cipher, protocol, latency)
export_pem() Export the certificate chain as PEM
verify_key_match() Verify a private key matches a certificate
convert_pfx_to_pem() Convert PKCS12/PFX to PEM files
convert_pem_to_pfx() Convert PEM cert and key to PKCS12/PFX
create_keystore() Create a PKCS12 keystore (Java compatible)
create_truststore() Create a PKCS12 truststore from CA certs

The network facing functions accept the shared mTLS and connection options (client_cert, client_key, pkcs12, cert_password, ca_cert, connect_to, resolve, proxy, noproxy) as keyword arguments.

Error handling

from dcert import (
    DcertError,            # base class
    DcertTimeoutError,     # the call exceeded its timeout
    DcertConnectionError,  # the subprocess died or the circuit breaker is open
    DcertToolError,        # the tool returned an error result (has .tool)
)

Only transport failures are retried, with exponential backoff and full jitter, and only for tools whose MCP annotations mark them read-only or idempotent (the typed client reads the backend's tool list once per session to decide). TypeError and ValueError surface immediately and cancellation is never swallowed. A call that times out closes the subprocess (it is reconnected on the next call) and counts against the circuit breaker; concurrent calls that fail together share one reconnect and count as one failure.

Command line

dcert-python                                   # stdio (for MCP clients such as Claude Code)
dcert-python --transport http --port 8080      # HTTP; bind 0.0.0.0 only behind a gateway
dcert-python --setup                           # download the binary and exit
dcert-python --binary /usr/local/bin/dcert-mcp # explicit binary
dcert-python --rate-limit 20 --bulkhead-max 4  # resilience flags
dcert-python --help                            # every option

dcert and dcert-mcp are thin wrappers that exec the Rust binaries with all arguments. A wrapper refuses to run when the only dcert-mcp it can find is itself (for example the pip console script on PATH), instead of exec-ing in a loop.

Configuration

Defaults live in the packaged dcert/config.yaml: the release URL, download limits, the install directory, the platform table, the environment variables forwarded to the subprocess, the server bind address, the transports and exporters offered by dcert-python, and every resilience value. dcert.load_config() returns them as an immutable record.

Resilience values can be overridden with DCERT_MCP_* environment variables (listed in dcert/resilience.py) and the dcert-python flags override those. A value outside its valid range (for example DCERT_MCP_CB_THRESHOLD=0 or DCERT_MCP_BULKHEAD_MAX=0) is rejected with a message naming the variable rather than crashing or hanging later. DCERT_MCP_NO_RETRY disables retries in both the proxy and the typed client, and DCERT_MCP_CONNECT_TIMEOUT bounds how long starting the subprocess and reading its tool list may take.

The proxy reads each tool's MCP annotations before applying caching or retries:

  • Caching (--cache) replays results only for tools marked read-only and idempotent. Tools that generate keys, issue or sign certificates, or change Vault state (create_csr, vault_issue, vault_sign, vault_renew, …) are always run.
  • Retry after a transport failure applies only to read-only or idempotent tools. Any other call surfaces the error instead of running a second time, because the first attempt may already have issued a certificate.

Binary discovery

  1. DCERT_MCP_BINARY (or DCERT_PATH for the dcert CLI); a relative path is resolved against the working directory, never through PATH
  2. The bundled binary in the package bin/ directory
  3. A compiled dcert-mcp on PATH (pip console script wrappers and the running launcher are skipped)
  4. Download from GitHub Releases: https only, redirects restricted to GitHub hosts, size and time capped, SHA256 verified before extraction, installed atomically under a lock

Downloaded binaries are installed into a directory owned by dcert, never into pip's scripts directory, so a download can never replace a console script: ~/.local/share/dcert/bin on Linux and macOS, %LOCALAPPDATA%\dcert\bin on Windows. Set DCERT_INSTALL_DIR to use another directory. dcert-python --setup downloads the binary ahead of time and prints where it was installed.

Environment variables forwarded to the binary

Category Variables
Proxy HTTP_PROXY, HTTPS_PROXY, NO_PROXY (and lowercase variants)
TLS SSL_CERT_FILE, SSL_CERT_DIR, REQUESTS_CA_BUNDLE
dcert DCERT_PATH, DCERT_MCP_TIMEOUT, DCERT_MCP_CONNECTION_TIMEOUT, DCERT_MCP_READ_TIMEOUT

Development

cd python
pip install -e ".[dev]"
ruff check src tests ../scripts
ruff format --check src tests ../scripts
mypy
pytest

License

MIT

Metadata

Release files for dcert 3.0.50

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dcert 3.0.50
File Size Uploaded
dcert-3.0.50.tar.gz 60.9 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for dcert 3.0.50
File
dcert-3.0.50-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details
dcert-3.0.50-py3-none-manylinux_2_35_x86_64.whl Python 3 none Linux glibc 2.35+ x86-64 Details
dcert-3.0.50-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details
dcert-3.0.50-py3-none-macosx_10_15_x86_64.whl Python 3 none macOS 10.15+ x86-64 Details
dcert-3.0.50-py3-none-any.whl Python 3 none any Details

Total release size: 46.2 MB

Release files / dcert-3.0.50.tar.gz

Download URL dcert-3.0.50.tar.gz
Size 60.9 kB
Tags Source
SHA-256 checksum
How to use checksums
794b10619636876f434b6639a04c7f967679a1f6136daacfd77fc71016149f77
BLAKE2b-256 checksum
How to use checksums
4c78df8c20e3ca8331bc85f1f5daaebe127e6c059da0d07a8cfa9cc530f49c7d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / dcert-3.0.50-py3-none-win_amd64.whl

Download URL dcert-3.0.50-py3-none-win_amd64.whl
Size 13.4 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
978eab6d019dd529db86fd77edd5531d84e8d50d78ee71bef2aeaed8d32f9213
BLAKE2b-256 checksum
How to use checksums
0a4db0f475d85f6be0a1df686d23428fd0f6e0752000f934dfebe22c77cc602f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / dcert-3.0.50-py3-none-manylinux_2_35_x86_64.whl

Download URL dcert-3.0.50-py3-none-manylinux_2_35_x86_64.whl
Size 11.4 MB
Tags Linux glibc 2.35+ x86-64 Python 3
SHA-256 checksum
How to use checksums
e137cc38dfb433baa0d945b78ec827cd1473c90e94320f0401b4be7a95d164d0
BLAKE2b-256 checksum
How to use checksums
8fe156af5144e5bb902d5759ead1891b9fd6aab24c6d8e1d02ea6bf2cae6f107
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / dcert-3.0.50-py3-none-macosx_11_0_arm64.whl

Download URL dcert-3.0.50-py3-none-macosx_11_0_arm64.whl
Size 10.3 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
250d87bac86028dc48456b6e51448d00750cf4c9385b4062db9ddba177555354
BLAKE2b-256 checksum
How to use checksums
b83e5f749c50dd0c7c681728f7a76c03c38e31711c5dd87942a57cb26ab2f928
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / dcert-3.0.50-py3-none-macosx_10_15_x86_64.whl

Download URL dcert-3.0.50-py3-none-macosx_10_15_x86_64.whl
Size 10.9 MB
Tags Python 3 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
dd6e2797e86ced9fbb84947f5699fa607408eba140a7d750c6590948f3778018
BLAKE2b-256 checksum
How to use checksums
440cc50caa4b15e7356909b504053be41f86ab4b5ce1b342961bb531b3c2e33a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log

Release files / dcert-3.0.50-py3-none-any.whl

Download URL dcert-3.0.50-py3-none-any.whl
Size 40.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7c07019f5cebdd853a2ef3a26a044ca5ef47190b631ee6be2862c1871a1b08ec
BLAKE2b-256 checksum
How to use checksums
4ba893cd9e9f08779e9ff5332a802d393b5070d1d429f6aec204ff5858d97ba0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page