Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Certman (BYOK) icon

Certman (BYOK)

Read your Certman private certificate authorities, CA chains, issued certificates and expiry dates with your own API key; no issuing, renewing or revoking

Unify Dynamics LLC

Tools5read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderCertmanunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Certman workspace does my key belong to?
Tools called
whoami
Which certificate authorities do I have in Certman?
Tools called
list_certificate_authorities
Show the details of Certman CA ca_1
Tools called
get_certificate_authority
Give me the certificate chain of Certman CA ca_1
Tools called
get_ca_chain
Which Certman certificates expire in the next 30 days?
Tools called
list_certificates

About

Certman (BYOK) lets an AI assistant read your own Certman data through the Certman API with a key you supply (Certman API key (starts with cm_; a key with read permissions is enough)). Read-only: 5 tools (whoami, list_certificate_authorities, get_certificate_authority, get_ca_chain, list_certificates). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.certman.app. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Certman. Certman and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Certman API (api.certman.app) with a BYOK key; documentation: https://certman.app/api/v1/openapi.json. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

5 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data5 tools
  • WhoamiShow which workspace and API key you are using and the per-CA permissions of the key.
  • List certificate authoritiesList private certificate authorities with name, subject, key algorithm, validity, parent CA and depth in the hierarchy; filter by root or…
  • Get certificate authorityGet the details of one certificate authority by id.
  • Get ca chainGet the PEM encoded public certificate chain of a certificate authority, from the CA up to the root.
  • List certificatesList issued certificates with common name, alternative names, key algorithm, validity, serial number and revocation state; filter by CA, status,…

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-certman.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 5 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-certman.connectorbay.com/mcp
RESTPOST https://byok-certman.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-certman.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Certman API key (starts with cm_; a key with read permissions is enough) in the X-Upstream-Key header (get one at certman.app).
  • Ask a question; the agent picks the right tool and answers from the live data.

Certman connector: questions and answers

What is the Certman connector?

Certman (BYOK) lets an AI assistant read your own Certman data through the Certman API with a key you supply (Certman API key (starts with cm_; a… It is a hosted MCP server with 5 tools such as Whoami, List certificate authorities, Get certificate authority, Get ca chain, List certificates, published by Unify Dynamics LLC. It is independent and not affiliated with Certman.

How do I connect Certman to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-certman.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-certman.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-certman.json.

Do I need a Certman account or API key?

Yes: this is a bring-your-own-key connector. Create a Certman API key (starts with cm_; a key with read permissions is enough) at https://certman.app/en/docs/getting-started and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Certman read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Certman connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Unsplash (BYOK)

Search and read Unsplash photos, collections and photographer profiles with your own API access key

Live · MCP + REST9 tools

Unstoppable Domains (BYOK)

Resolve Unstoppable Domains and ENS names to their on-chain records and registry details with your own Resolution Service API key

Live · MCP + REST5 tools

Unstructured (BYOK)

Read your Unstructured workflows, jobs, per-file processing status, connectors, templates and metered usage with your own API key

Live · MCP + REST12 tools

UpCloud (BYOK)

Read your UpCloud cloud servers, storages, IP addresses, networks, zones and account limits with your own API bearer token

Live · MCP + REST7 tools

updown.io (BYOK)

Read your updown.io website monitors: status, uptime, downtime periods, response-time metrics, SSL and domain expiry with BYOK

Live · MCP + REST5 tools

Upstash (BYOK)

Read your Upstash Redis databases, usage stats, backups, teams and audit log with BYOK

Live · MCP + REST7 tools

Documentation

Back to top

Certman (BYOK) — connector documentation

  • MCP endpoint: https://byok-certman.connectorbay.com/mcp
  • REST API: POST https://byok-certman.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-certman.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Certman Certman API key (starts with cm_; a key with read permissions is enough), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-certman.connectorbay.com/health · Tool schemas: https://byok-certman.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-certman · agent@connectorbay.com

What Certman (BYOK) is for

Certman (BYOK) lets an AI assistant read your own Certman data through the Certman API with a key you supply (Certman API key (starts with cm_; a key with read permissions is enough)). Read-only: 5 tools (whoami, list_certificate_authorities, get_certificate_authority, get_ca_chain, list_certificates). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.certman.app. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Certman. Certman and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Certman workspace does my key belong to?"
  • "Which certificate authorities do I have in Certman?"
  • "Show the details of Certman CA ca_1"
  • "Give me the certificate chain of Certman CA ca_1"
  • "Which Certman certificates expire in the next 30 days?"

What it does

  • whoami: Show which workspace and API key you are using and the per-CA permissions of the key.
  • list_certificate_authorities: List private certificate authorities with name, subject, key algorithm, validity, parent CA and depth in the hierarchy; filter by root or intermediate or by parent.
  • get_certificate_authority: Get the details of one certificate authority by id.
  • get_ca_chain: Get the PEM encoded public certificate chain of a certificate authority, from the CA up to the root.
  • list_certificates: List issued certificates with common name, alternative names, key algorithm, validity, serial number and revocation state; filter by CA, status, name, creation date or days until expiry.

BYOK key

You bring your own Certman Certman API key (starts with cm_; a key with read permissions is enough) (https://certman.app/en/docs/getting-started). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.certman.app over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Certman API (api.certman.app) with a BYOK key; documentation: https://certman.app/api/v1/openapi.json. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Certman. Certman and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Certman account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Certman (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Certman (BYOK) is. Certman (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Certman data: Read your Certman private certificate authorities, CA chains, issued certificates and expiry dates with your own API key; no issuing, renewing or revoking. You bring your own Certman Certman API key (starts with cm_; a key with read permissions is enough); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Certman call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.certman.app, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Certman rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Certman receives. The request we make on your behalf, including the key and the arguments, under Certman's own terms and privacy policy. Certman acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Certman gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Certman data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Certman (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Certman at any time to end all access.

Children. Certman (BYOK) is a general-audience service operated by the adult using the assistant, under Certman's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Certman (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Certman (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Certman (BYOK) provides: Read your Certman private certificate authorities, CA chains, issued certificates and expiry dates with your own API key; no issuing, renewing or revoking. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Certman credentials and only access data you are allowed to access. Certman's terms apply to your use of Certman; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Certman. Certman and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Certman returns, lightly trimmed; it may be incomplete, delayed or changed by Certman. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Certman account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Certman's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Certman may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Certman key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Certman takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-certman

Certman (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Certman (BYOK) never asks for them.

Get Certman (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Certman Certman API key (starts with cm_; a key with read permissions is enough). Create one at https://certman.app/en/docs/getting-started, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Certman. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Certman.