CertBridge MCP

io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLCPublished by GitHub account CYAN-ECLIPSE-TECHNOLOGIES-LLCv0.2.0Updated Oct 26, 2026

ACME certificate lifecycle for agents: order, HTTP-01/DNS-01 validation, download, renewal.

Overview

AI-generated overview

Local MCP server that lets an assistant run the ACME certificate lifecycle: ordering, HTTP-01/DNS-01 validation, downloading and renewing TLS certificates.

What you can do
  • Order certificates through ACME from an assistant session
  • Complete domain validation via HTTP-01 or DNS-01 challenges
  • Download issued certificates to a local state directory
  • Renew existing certificates
  • Keep ACME account keys, orders, certificates and an audit log in one state directory
When to use it
Useful when you want an assistant to obtain or renew TLS certificates for your own domains without leaving the chat, for example setting up HTTPS on a small server or automating renewal checks.
Requirements
Runs as a local process over stdio, distributed as a Docker image, so Docker is needed. The CERTBRIDGE_HOME environment variable sets the state directory for account keys, orders, certificates and the audit log; it defaults to a certbridge-state folder beside the server. Network access to an ACME certificate authority and to the domains being validated is required.
Before you install
It stores ACME account keys and private certificate material in the state directory, so protect that directory. Ordering and renewing certificates changes real public certificate state and may hit certificate authority rate limits. DNS-01 validation may require DNS credentials or record changes on your domains. No authentication is declared for the server itself.

Installation

In SourceWeft

  1. Open CertBridge MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v0.2.0LatestOct 26, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.