Add 10 new MCP servers from Dockyard repository

[JAORMX]

Summary

This PR adds 10 new MCP servers that are available through the Dockyard repository (https://github.com/stacklok/dockyard). These servers are containerized and include proper provenance information for supply chain security.

Added MCP Servers

1. aws-diagram-mcp-server (5,291 ⭐)

   • AWS Labs Model Context Protocol server for creating diagrams
   • Tools: generate_diagram, get_diagram_examples, list_icons

2. aws-documentation-mcp-server (5,291 ⭐)

   • AWS Labs server for AWS Documentation access
   • Tools: read_documentation, search_documentation, recommend

3. browserbase-mcp-server (2,401 ⭐)

   • Cloud browser automation with Browserbase and Stagehand
   • Tools: session management, navigation, extraction, observation

4. context7 (25,096 ⭐)

   • Upstash Context7 for vector search and context management
   • Tools: resolve-library-id, get-library-docs

5. graphlit-mcp-server (346 ⭐)

   • Knowledge base platform for ingestion, search, and RAG
   • Tools: content ingestion, web crawling, RAG operations, data connector integrations

6. heroku-mcp-server (55 ⭐)

   • Heroku platform management
   • Tools: app management, dyno control, PostgreSQL operations, pipeline management

7. mcp-clickhouse (485 ⭐)

   • ClickHouse database integration with optional chDB support
   • Tools: run_select_query, list_databases, list_tables, run_chdb_select_query

8. mcp-server-box (43 ⭐)

   • Box API integration for file operations and AI-based querying
   • Tools: file operations, AI tools, document generation, metadata management

9. sentry-mcp-server (292 ⭐)

   • Sentry's MCP service for debugging and monitoring
   • Tools: issue management, trace analysis, event search, team/project management

10. supabase-mcp-server (1,940 ⭐)

    • Supabase project management and database operations
    • Tools: database operations, edge functions, branching, storage management

Key Features

• ✅ All servers are containerized via ghcr.io/stacklok/dockyard
• ✅ Include proper provenance information for supply chain security
• ✅ Network permissions configured appropriately for each service
• ✅ Environment variables documented with proper secret handling
• ✅ All entries validated with task validate
• ✅ GitHub stars fetched via regup tool

Testing

# Validation passed
$ task validate
✓ All 46 registry entries are valid

Security Considerations

• All containers include Sigstore provenance information
• Network permissions are restricted to necessary hosts/ports
• Sensitive environment variables are properly marked as secrets
• Containers are built and signed via GitHub Actions workflows