toolhive-catalog and toolhive-registry-server
The catalog provides the curated data source of MCP servers while the registry server implements the standardized API layer for programmatic access to that catalog, making them complements designed to work together in a registry infrastructure.
About toolhive-catalog
stacklok/toolhive-catalog
ToolHive's registry catalog of MCP servers
Provides both container-based (Docker/OCI) and remote HTTP-accessible MCP servers via a standardized `server.json` schema with ToolHive-specific metadata extensions for tier classification, permission policies, and Sigstore provenance tracking. Includes a complementary skills registry for composable prompt workflows that declaratively reference and combine server tools, validated through automated catalog checks.
About toolhive-registry-server
stacklok/toolhive-registry-server
An API server that implements the official MCP Registry API, providing standardised access to MCP servers from multiple backends, including file-based and other API-compliant registries.
Supports multiple registry sources (Git, file, API, Kubernetes) with automatic background synchronization and configurable retry logic, aggregating them into a unified catalog. Built with clean layered architecture using Chi router for HTTP handling and PostgreSQL for scalable metadata storage. Integrates with ToolHive Enterprise UI and Kubernetes operators through OAuth 2.0/OIDC authentication, enabling enterprise governance with audit trails and standards-compliant API endpoints.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work