modelcontextprotocol/registry

AI Summary: Enhance the existing `/v0/health` endpoint of the MCP Registry service to include detailed health information such as database connection status, service uptime, memory usage, and version information. This involves modifying the `internal/api/handlers/v0/health.go` file to add these checks and metrics while maintaining backward compatibility with the existing response format. The goal is to provide a more comprehensive health check for monitoring and diagnostics.

AI Summary: Implement CORS middleware in the Go-based MCP Registry API to enable cross-origin requests from web browsers. This involves adding middleware to the existing HTTP router to set appropriate CORS headers (Access-Control-Allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers, Access-Control-Max-Age) and handle preflight OPTIONS requests. Testing should be performed to ensure all API endpoints function correctly with CORS enabled.

AI Summary: Debug and fix the Swagger UI handler in `internal/api/handlers/v0/swagger.go` to make the API documentation accessible at `/v0/swagger/index.html`. Ensure the UI loads correctly, displays all documented endpoints, and allows interactive testing. The OpenAPI spec is located in `internal/docs/swagger.yaml`.

AI Summary: Implement CORS middleware in the Go-based MCP Registry service to allow cross-origin requests from specified origins. This involves adding middleware to handle CORS headers, preflight requests, and configuring allowed origins, methods, and headers via environment variables. Testing and documentation updates are also required.

AI Summary: Enhance the existing health check endpoint of the MCP Registry service to return more detailed status information, including database connectivity, service dependencies, application version, uptime, and optionally memory usage. The solution must maintain backward compatibility and include comprehensive testing.

AI Summary: Debug and fix the Swagger UI handler in the MCP Registry service. The `/v0/swagger/index.html` endpoint is currently inaccessible, preventing users from interacting with the API documentation. The solution involves investigating the routing and file serving logic within `internal/api/handlers/v0/swagger.go`, ensuring the OpenAPI specification (`docs/openapi.yaml` or `internal/docs/swagger.yaml`) is correctly loaded and served, and verifying all API endpoints are documented and testable within the UI.