CertBridge MCP
OCI · GHCR.IO/CYAN-ECLIPSE-TECHNOLOGIES-LLC/CERTBRIDGE-MCP
ACME certificate lifecycle for agents: order, HTTP-01/DNS-01 validation, download, renewal.
Available components
Last scanned (20 hours ago)
Scores higher than 36% of OCI servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 921 tokens (~92/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 27 Oct 26 0
- Stability: 0.00 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 72 → 92 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Schema quality: fair → good functional
- 26 Oct 26 28
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed oci/ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_log ~53
The append-only trail: accounts, orders, challenges computed/placed, validation polls, downloads, installs, status checks. Mirrored to audit.jsonl.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| subject | string | – | – |
No output schema declared.
No examples provided.
certificate_status ~53
Parse any PEM certificate with openssl x509: issuer, subject, SANs, validity window, days left, renewal-due flag (<=30 days), self-signed detection.
| Name | Type | Req | Description |
|---|---|---|---|
| pem_path | string | yes | – |
No output schema declared.
No examples provided.
complete_validation ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| force_dns_trigger | boolean | – | – |
| order_id | string | yes | – |
| poll_seconds | integer | – | – |
| skip_trigger | boolean | – | – |
No output schema declared.
No examples provided.
dns_check ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_txt_value | string | – | – |
| order_id | string | – | – |
| txt_name | string | – | – |
No output schema declared.
No examples provided.
download_certificate ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
No output schema declared.
No examples provided.
get_challenges ~127
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).
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_type | string | – | – |
| order_id | string | yes | – |
No output schema declared.
No examples provided.
install_certificate ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cert_path | string | yes | – |
| fullchain_path | string | yes | – |
| install_dir | string | yes | – |
| key_path | string | yes | – |
| transport | string | – | – |
No output schema declared.
No examples provided.
place_challenge ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| docroot_path | string | yes | – |
| file_content | string | yes | – |
| file_name | string | yes | – |
| order_id | string | yes | – |
| transport | string | – | – |
No output schema declared.
No examples provided.
register_account ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ca | string | yes | – |
| eab_hmac_b64 | string | – | – |
| eab_kid | string | – | – |
| string | – | – |
No output schema declared.
No examples provided.
request_certificate ~50
Open an ACME order for a list of domains on a registered account. Returns order id, status, expiry, and authorization URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| domains | array | yes | – |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/cyan-eclipse-technologies-llc/certbridge-mcp
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.
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 32 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.