toolhive-registry-server
Verified Safeby stacklok
Overview
The central metadata hub for enterprise Model Context Protocol (MCP) server governance and discovery, implementing the official MCP Registry API specification.
Installation
docker run -d --name registry-api -p 8080:8080 -v $(pwd)/examples:/config:ro ghcr.io/stacklok/toolhive/thv-registry-api:latest serve --config /config/config-git.yamlEnvironment Variables
- THV_REGISTRY_LOG_LEVEL
- THV_REGISTRY_ADDRESS
- THV_REGISTRY_REGISTRYNAME
- THV_REGISTRY_AUTH_MODE
- THV_REGISTRY_INSECURE_URL
- THV_REGISTRY_DATABASE_HOST
- THV_REGISTRY_DATABASE_PORT
- THV_REGISTRY_DATABASE_USER
- THV_REGISTRY_DATABASE_DATABASE
- THV_REGISTRY_DATABASE_SSLMODE
- THV_REGISTRY_DATABASE_MIGRATIONUSER
- THV_REGISTRY_DATABASE_MAXOPENCONNS
- THV_REGISTRY_DATABASE_MAXIDLECONNS
- THV_REGISTRY_DATABASE_CONNMAXLIFETIME
- PGPASSFILE
- CONFIG_FILE
Security Notes
The project emphasizes security with clear guidelines (`SECURITY.md`), OAuth 2.0/OIDC authentication enabled by default, and recommendations for production (`sslMode: verify-full`, `pgpass`). However, default hardcoded passwords (`app_password`, `migration_password`) are present in `docker/postgres-init.sh` for initialization, which, while common in examples, is a minor concern if not replaced in production. Some example `permissions` configurations for MCP servers in the registry data allow `insecure_allow_all`, highlighting a potential for misconfiguration within the ecosystem the server manages, rather than the server itself.
Similar Servers
registry
The MCP Registry serves as a centralized metadata repository for publicly-available MCP servers, facilitating discovery and publishing of server information for clients and aggregators.
Unla
Transforms existing MCP Servers and APIs into MCP protocol-compliant endpoints through configuration, enabling LLM tool calling without code changes.
tmcp
A server implementation for the Model Context Protocol (MCP) to enable LLMs to access external context and tools.
mcp-registry
The Model Context Protocol (MCP) Registry centralizes and structures installation configurations for various MCP servers, enabling easy discovery and integration into MCP clients and hubs.