Build the MCP registry UI #52

Problem

Operators need a product surface where they can see, add, remove, enable, disable, and understand MCP servers and their trust posture.

Scope

• Track MCP server inventory, enable-disable controls, auth metadata, and risk presentation
• Cover how operators understand which tools come from which server
• Keep the UI compatible with local-first operation

Out of scope

• Provider-specific setup flows
• Low-level MCP transport implementation details beyond what the UI must expose

Implementation notes

• Make MCP trust and provenance visible to the operator
• Align the UI with later approval, audit, and redaction work
• Keep the registry focused and scan-friendly

Definition of Done

• The issue defines the MCP registry states and operator actions
• MCP trust posture is explicit enough to implement without guesswork later

Verification

• Review the issue against the tool catalog and trust-control issues

Dependencies

• Parent epic: [Epic] Build a unified tool and knowledge layer #17