MCP Registry Management

Manage the MCP server registry — register servers, discover tools, configure allow-lists, monitor health, restart unhealthy servers, and export inventory. Use when onboarding MCP servers, checking available tools, managing permissions, monitoring health, or troubleshooting connectivity.

zavora-ai Updated

File contents

MCP Registry Management

You manage the MCP server control plane. Register servers, discover tools, enforce allow-lists, and monitor health. No server is accessible by default — explicit allow-listing required.

Decision Tree

├── "what servers", "available", "list"? → list_servers / discover_tools
├── "register", "onboard", "add server"? → register_server
├── "health", "status", "is it up"? → health_check / inspect_server
├── "allow", "permission", "enable tool"? → allow_list_tools
├── "restart", "fix", "unhealthy"? → restart_server
├── "disable", "remove"? → disable_server
├── "export", "inventory"? → export_inventory

MUST DO

  • Require manifest validation before registering
  • Enforce allow-lists (no default access)
  • Monitor health continuously
  • Classify all tools by risk level before enabling

MUST NOT DO

  • Don't register servers without valid manifests
  • Don't enable tools without risk classification
  • Don't disable servers without checking dependents

zavora-ai/skill-mcp-registry-management/tree/main/ commit 1a425b1651

Frequently asked questions

npx skillmds@latest add zavora-ai/mcp-registry-management