Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

IONOS Container Registry (BYOK) — connector documentation

  • MCP endpoint: https://byok-ionos-container-registry.connectorbay.com/mcp
  • REST API: POST https://byok-ionos-container-registry.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-ionos-container-registry.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own IONOS Container Registry IONOS Cloud API token (JWT), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-ionos-container-registry.connectorbay.com/health · Tool schemas: https://byok-ionos-container-registry.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-ionos-container-registry · agent@connectorbay.com

What IONOS Container Registry (BYOK) is for

IONOS Container Registry (BYOK) lets an AI assistant read your own IONOS Container Registry data through the IONOS Container Registry API with a key you supply (IONOS Cloud API token (JWT)). Read-only: 5 tools (list_registries, get_registry, list_repositories, list_artifacts, list_registry_locations). 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.ionos.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by IONOS Container Registry. IONOS Container Registry 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 container registries do I have on IONOS and how much do they store?"
  • "Show my IONOS container registry r1."
  • "Which repositories in my IONOS registry were pushed to recently?"
  • "Which images in my IONOS registry have fixable vulnerabilities?"
  • "Where can I create an IONOS container registry?"

What it does

  • list_registries: List your private container registries with name, hostname, location, state, storage used (bytes), garbage-collection schedule and vulnerability-scanning feature. Uses a continuation token for paging.
  • get_registry: Get one container registry: name, hostname, location, state, storage used, garbage-collection schedule and scanning feature.
  • list_repositories: List the repositories of a registry with artifact count, pull and push counts, and last push and pull time.
  • list_artifacts: List image artifacts of a registry with repository, digest, tags, push and pull counts, last scan time and vulnerability counts.
  • list_registry_locations: List the IONOS locations where container registries can be created.

BYOK key

You bring your own IONOS Container Registry IONOS Cloud API token (JWT) (https://docs.ionos.com/cloud/set-up-ionos-cloud/management/identity-access-management/token-manager). 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.ionos.com 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 IONOS Container Registry API (api.ionos.com) with a BYOK key; documentation: https://docs.ionos.com/cloud/api-reference/containers/private-container-registry. 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 IONOS Container Registry. IONOS Container Registry 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 IONOS Container Registry account.

Built for: Worldwide. Languages: English.