# CertBridge MCP (oci · ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp)

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

- Trust score: 33/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp`: 33/100 (this document), [markdown](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-certbridge/ghcr-io-cyan-eclipse-technologies-llc-certbridge-mcp.md), [page](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-certbridge/ghcr-io-cyan-eclipse-technologies-llc-certbridge-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 9 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 921 tokens (~92/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the CertBridge MCP server?

CertBridge MCP runs locally as a container image, launched with docker run --rm -i -e CERTBRIDGE_HOME ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cyan-eclipse-technologies-llc-certbridge -- docker run --rm -i -e CERTBRIDGE_HOME ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Cursor

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-certbridge": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CERTBRIDGE_HOME",
        "ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0"
      ]
    }
  }
}
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

### VS Code

```json
{
  "servers": {
    "cyan-eclipse-technologies-llc-certbridge": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CERTBRIDGE_HOME",
        "ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0"
      ]
    }
  }
}
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Codex

```bash
codex mcp add cyan-eclipse-technologies-llc-certbridge -- docker run --rm -i -e CERTBRIDGE_HOME ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyan-eclipse-technologies-llc-certbridge": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "CERTBRIDGE_HOME",
        "ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0"
      ],
      "enabled": true
    }
  }
}
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Hermes

```yaml
mcp_servers:
  cyan-eclipse-technologies-llc-certbridge:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "CERTBRIDGE_HOME", "ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0"]
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Netclaw

```json
{
  "McpServers": {
    "cyan-eclipse-technologies-llc-certbridge": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CERTBRIDGE_HOME",
        "ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0"
      ]
    }
  }
}
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Other

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-certbridge": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CERTBRIDGE_HOME",
        "ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp:0.2.0"
      ]
    }
  }
}
```

This image reads CERTBRIDGE_HOME. Set it in your client's env block for this server; docker run -e passes it through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 33, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 32, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 31, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 30, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 29, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 28, 0)

- [security regression] Stability: 0.00 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Schema quality: 72 → 92
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Schema quality: fair → good

### 2026-10-26 (score 28)

First indexed and scored.

## MCP tools (10)

### `register_account` (~116 tokens)

Create an ACME account at a CA (letsencrypt / letsencrypt-staging / zerossl-eab). Generates an RSA account key via openssl into the server state dir and returns the account URL (kid). ZeroSSL requires eab_kid + eab_hmac_b64 from the ZeroSSL dashboard. Staging is always labelled staging.

Input parameters:

- `ca` (string, required)
- `eab_hmac_b64` (string)
- `eab_kid` (string)
- `email` (string)

### `request_certificate` (~50 tokens)

Open an ACME order for a list of domains on a registered account. Returns order id, status, expiry, and authorization URLs.

Input parameters:

- `account_id` (string, required)
- `domains` (array, required)

### `get_challenges` (~127 tokens)

For an order: fetch authorizations and compute the challenge for each domain — token and key authorization for every type; HTTP-01 adds the exact file name/content to place at <docroot>/.well-known/acme-challenge/, DNS-01 adds the txt_name/txt_value TXT record to create. challenge_type: http-01 (default, v0.1 behaviour) | dns-01 | auto (per domain: http-01 if offered, else dns-01; mixed orders legal).

Input parameters:

- `challenge_type` (string)
- `order_id` (string, required)

### `dns_check` (~136 tokens)

Check DNS-01 TXT propagation for an order's computed challenges via DNS-over-HTTPS (Google DoH, no fallback resolver). Per domain returns exactly one state: propagated (expected value is any of the returned TXT set) | wrong_value | no_record | resolver_error. Read-only; persists last_dns_check on the order, which is what complete_validation's DNS gate reads. Optional txt_name + expected_txt_value overrides run a one-off check that persists nothing (audit only), with or without an order_id.

Input parameters:

- `expected_txt_value` (string)
- `order_id` (string)
- `txt_name` (string)

### `place_challenge` (~88 tokens)

Write one challenge file into a docroot. v0 transport: local (real write to docroot_path). Remote transports (HostBridge channel) are declared and return an explicit not-yet.

Input parameters:

- `docroot_path` (string, required)
- `file_content` (string, required)
- `file_name` (string, required)
- `order_id` (string, required)
- `transport` (string)

### `complete_validation` (~148 tokens)

Trigger the CA's validation (the challenge type selected per domain by get_challenges) for the order's authorizations, then poll authorization + order status. DNS-01 domains are gated: without a persisted dns_check showing propagated for all of them, this refuses with dns_not_propagated and triggers nothing — force_dns_trigger=true is the narrow, audited override (skip_trigger does not waive the gate). HTTP-01 passes require the challenge file publicly reachable on the domain — a local simulator cannot pass, and the tool says so.

Input parameters:

- `force_dns_trigger` (boolean)
- `order_id` (string, required)
- `poll_seconds` (integer)
- `skip_trigger` (boolean)

### `download_certificate` (~54 tokens)

When the order is ready: generate the domain key + CSR via openssl, finalize, and download the PEM chain into the state dir. Errors plainly if the order is not valid yet.

Input parameters:

- `order_id` (string, required)

### `install_certificate` (~96 tokens)

Install a downloaded cert. v0 transport: local (writes cert.pem / fullchain.pem / privkey.pem to install_dir and reports the paths). cPanel UAPI SSL::install_ssl is declared and returns an explicit not-yet.

Input parameters:

- `cert_path` (string, required)
- `fullchain_path` (string, required)
- `install_dir` (string, required)
- `key_path` (string, required)
- `transport` (string)

### `certificate_status` (~53 tokens)

Parse any PEM certificate with openssl x509: issuer, subject, SANs, validity window, days left, renewal-due flag (<=30 days), self-signed detection.

Input parameters:

- `pem_path` (string, required)

### `audit_log` (~53 tokens)

The append-only trail: accounts, orders, challenges computed/placed, validation polls, downloads, installs, status checks. Mirrored to audit.jsonl.

Input parameters:

- `limit` (integer)
- `subject` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-certbridge/ghcr-io-cyan-eclipse-technologies-llc-certbridge-mcp#diagnostics

## Score history

- 2026-11-05: 33
- 2026-11-04: 32
- 2026-11-03: 32
- 2026-11-02: 31
- 2026-11-01: 31
- 2026-10-31: 30
- 2026-10-30: 30
- 2026-10-29: 29
- 2026-10-28: 29
- 2026-10-27: 28
- 2026-10-26: 28

## Common questions

### What is the CertBridge MCP server?

CertBridge MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/certbridge. ACME certificate lifecycle for agents: order, HTTP-01/DNS-01 validation, download, renewal. This page covers its container image (ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp).

### Is the CertBridge MCP server safe to use?

CertBridge MCP scores 33 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CertBridge MCP server expose?

CertBridge MCP exposes 10 tools: register_account, request_certificate, get_challenges, dns_check, place_challenge, and 5 more. Their descriptions and schemas cost roughly 921 tokens of context every time the server is loaded.

### Is the CertBridge MCP server still maintained?

CertBridge MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp
- Website: https://cetech.ai/
- Changelog RSS feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-certbridge/ghcr-io-cyan-eclipse-technologies-llc-certbridge-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-certbridge/ghcr-io-cyan-eclipse-technologies-llc-certbridge-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-certbridge/ghcr-io-cyan-eclipse-technologies-llc-certbridge-mcp