Registry Overview
The Helmet Registry is your central hub for managing Model Context Protocol (MCP) servers. It provides a unified interface for discovering, scanning, and publishing MCP servers across your organization.
What is the Registry?
The Registry serves as a catalog of all MCP servers in your environment, offering:
- Server Discovery: Browse and search available MCP servers
- Security Scanning: Automated vulnerability and compliance checks
- Publishing Workflow: Promote servers from development to production
- Artifact Management: View and manage server tools, prompts, and resources
Key Concepts
MCP Servers
Model Context Protocol servers that provide tools, prompts, and resources to AI models. Examples include:
- Database connectors
- API integrations
- File system access
- Custom business logic
Repository Types
Servers can be sourced from various repositories:
- GitHub repositories
- Docker containers
- Local file systems
- Package registries
Registry Workflow
- Add Server: Register a new MCP server in the system
- Security Scan: Automatic analysis for vulnerabilities and issues
- Review Results: Examine scan findings and remediate issues
- Publish: Approve servers for deployment and use
- Deploy: Use published servers in your environments
Dashboard Features
Server List View
The main registry view displays:
- Server name and type
- Repository source
- Current status (Draft/Published/Scanning)
- Quick action buttons
Filtering and Search
- Filter by status (All, Published, Draft, Pending)
- Search by server name
- Sort by various criteria
Server Actions
For each server, you can:
- Edit configuration
- View artifacts
- Run security scans
- Unpublish or delete
- Deploy to environments
Security Integration
Every server in the registry undergoes automated security scanning that checks for:
- Known vulnerabilities in dependencies
- Exposed secrets or credentials
- Unsafe tool implementations
- Compliance with organizational policies