docs: Add MCP registry browser to the community-projects.md page

[vemonet]

Motivation and Context

Added a fully client-side browser for MCP registry APIs to the community-projects.md documentation page: https://vemonet.github.io/mcp-registry

I built it because I was missing a way to easily configure a server and export the configuration (existing browsers I have found show the available parameters, but you still need to manually build the JSON):

• It shows a user friendly form that enables to configure MCP servers based on their registry entry, making it easier to understand and fill the configuration required for deploying a server (instead of having to read through JSON, and manually build another JSON). Then users can either copy the generated config or install in client with custom URL handler like VSCode/cursor in 1 click
• It is a thin client UI layer over the existing registry API, it does not offer additional classification, complex filtering, or semantic search (we don't use an additional server or database). So it is more of a tool to make it user friendly to directly access a raw registry content and inspects available servers, than an opinionated browser with advanced search capabilities

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context