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
One command — thv run oci-registry