get_image_infoLABSCO SUMMARY
Registry questions answered without a pull.
Checking which architecture an image was built for, or which tag is newest, normally costs a pull and an inspect. These four calls read it out of the registry directly.
What it is
An SSE-based MCP server for OCI registries. Point it at an image reference and it returns the image's information, its manifest or its config; point it at a repository and it lists the tags.
What you get
- An image's digest, size, architecture, OS, creation date and layer count
- The tags in a repository
- The image manifest
- The image config
Requirements
Nothing for public registries. For a private one, run it through ToolHive: store the registry credential as a ToolHive secret and hand that secret to the server at launch, rather than pasting the token into a config file.
Setup effort
Follow the published steps — thv client setup
USE CASES
01
Checking an image is built for the architecture you deploy on
Architecture and OS come back with the digest, before anything is downloaded.
02
Finding the newest tag on a base image
List the repository's tags rather than guessing at a version scheme.
03
Seeing what is in a layer stack before adopting an image
The manifest shows the layers as the registry holds them.
04
Reading the entrypoint and environment an image ships with
The config is where those are recorded, and it is one call.
05
Comparing two images without downloading either
Info and manifest for both, side by side.
4 tools
Listed in project docs. Your client may show a different list.
list_tagsget_image_manifestget_image_configBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation. All four tools only read and work against public registries with no account. For a private registry, use OCI_TOKEN, OCI_USERNAME with OCI_PASSWORD, or ~/.docker/config.json; OCI_PASSWORD does nothing alone.
Requires
- ToolHive (thv CLI)
- A container runtime: Docker, Podman, Colima or Rancher Desktop
INSTALLATION
Connect your client
Server setup
Any ToolHive client
Install ToolHive (see https://docs.stacklok.com/toolhive/guides-cli/install)
TERMINAL
thv client setup
thv run oci-registry
