MCP OCI Registry Server
A Model Context Protocol (MCP) server for querying OCI container registries. Provides tools and prompts for interacting with registries like Docker Hub, GHCR, and other OCI-compatible registries.
README
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/indexes - Support 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.txt
Usage
Run in stdio mode (default)
By default, the server runs over stdio which is what most MCP clients expect:
python server.py
The 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 run
Or manually:
uvicorn server:asgi_app --host 127.0.0.1 --port 8888
Run with Docker Compose
For development with hot reload:
make compose-up
Or manually:
docker compose up --build
Example 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.py
Development
Run tests:
make test
Available 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 dependencies - Integration tests (
tests/test_integration_http.py) - Test full MCP protocol flow using FastMCP Client
Run all tests:
pytest -v
Extending
Add new tools:
- Add the function to
tools.py - Register it in
server.py:mcp.tool(your_function)
Add new prompts:
- Add the prompt function to
prompts.py - Register it in
server.py:mcp.prompt(your_prompt)
License
Apache
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。