MCP OCI Registry Server
Provides tools for querying OCI container registries (e.g., Docker Hub) to list tags and fetch manifest details including architectures, digests, and annotations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP OCI Registry ServerShow tags for library/python on Docker Hub"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP OCI Registry Server
A Model Context Protocol (MCP) server for querying OCI container registries. Built with the fastmcp framework, this server provides tools and prompts for interacting with container registries like Docker Hub, GHCR, and other OCI-compatible registries.
Features
Tools:
ping- Health check toollist_oci_tags- List all tags for an OCI repositoryget_oci_details- Fetch manifest details including architectures, digest, and annotations
Prompts:
list_tags_prompt- Instructions for listing repository tagslist_architectures_prompt- Instructions for listing supported architectureslist_digests_prompt- Instructions for retrieving image digestslist_annotations_prompt- Instructions for listing OCI annotations
Additional Features:
Custom
NonValidatingRegistryclass that bypasses jsonschema validation for manifest lists/indexesSupport for multi-architecture images
Optional authentication (username/password)
HTTP health check endpoint (
/healthz)Docker support with docker-compose for development
Requirements
Python 3.11+
Docker (optional, for containerized deployment)
Installation
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
pip install -r requirements.txtUsage
Run in stdio mode (default)
By default, the server runs over stdio which is what most MCP clients expect:
python server.pyThe process will wait for JSON-RPC requests over stdin/stdout. Typically you do not run it manually; it is launched by an MCP-compatible client.
Run with uvicorn (HTTP)
For HTTP access, use the Makefile:
make runOr manually:
uvicorn server:asgi_app --host 127.0.0.1 --port 8888Run with Docker Compose
For development with hot reload:
make compose-upOr manually:
docker compose up --buildExample Tool Usage
List tags:
# Using FastMCP Client
from fastmcp import Client, FastMCP
import server
client = Client(server.mcp)
async with client:
tags = await client.call_tool("list_oci_tags", {
"registry": "registry-1.docker.io",
"repository": "library/alpine"
})
print(tags.data) # ['latest', '3.22.2', 'edge', ...]Get OCI details:
details = await client.call_tool("get_oci_details", {
"registry": "registry-1.docker.io",
"repository": "library/alpine",
"reference": "3.22.2"
})
print(details.data)
# {
# "digest": "sha256:...",
# "architectures": ["amd64", "arm64", ...],
# "annotations": {...}
# }MCP Client Configuration (Claude Desktop)
Add an entry in your Claude Desktop MCP config (~/.cursor/mcp.json or similar):
{
"mcpServers": {
"mcp-oci-registry": {
"command": "/path/to/.venv/bin/python",
"args": [
"/path/to/mcp-oci-registry/server.py"
],
"env": {}
}
}
}Adjust paths as needed for your environment.
Project Layout
mcp-oci-registry/
├── server.py # MCP server entrypoint
├── tools.py # Tool functions (ping, list_oci_tags, get_oci_details)
├── prompts.py # Prompt templates
├── registry.py # NonValidatingRegistry class
├── __init__.py # Package initialization
├── requirements.txt # Python dependencies
├── Dockerfile # Container image definition
├── docker-compose.yml # Development environment
├── Makefile # Common operations
└── tests/ # Test suite
├── test_tools.py
└── test_integration_http.pyDevelopment
Run tests:
make testAvailable Make targets:
make install- Install dependenciesmake run- Run server with uvicornmake test- Run test suitemake docker-build- Build Docker imagemake docker-run- Run Docker containermake compose-up- Start with docker-composemake compose-down- Stop docker-composemake compose-logs- View docker-compose logs
Testing
The project includes both unit tests and integration tests:
Unit tests (
tests/test_tools.py) - Test individual tool functions with mocked dependenciesIntegration tests (
tests/test_integration_http.py) - Test full MCP protocol flow using FastMCP Client
Run all tests:
pytest -vExtending
Add new tools:
Add the function to
tools.pyRegister it in
server.py:mcp.tool(your_function)
Add new prompts:
Add the prompt function to
prompts.pyRegister it in
server.py:mcp.prompt(your_prompt)
License
Apache
This server cannot be deployed
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A registry of AI agent tools — MCP servers, APIs, CLIs, SDKs — kept current by automated ingestion.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides tools for interacting with Docker images, containers, and registries, enabling AI assistants to search, analyze, and manage Docker resources through a standardized interface.1MIT

OpenTofu MCP Serverofficial
AlicenseAqualityBmaintenanceA Model Context Protocol server that allows AI assistants to search for and retrieve information about OpenTofu providers, modules, resources, and data sources from the OpenTofu Registry.5160 npm108Mozilla Public 2.0- AlicenseNot gradedqualityAmaintenanceAI-first MCP server discovery tool that enables agents to search, inspect, and install MCP servers from multiple registries.12AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA production-ready Model Context Protocol (MCP) server that provides comprehensive DockerHub integration for AI assistants. This server enables AI assistants to search, analyze, and manage Docker images through standardized MCP tools.MIT