MCP Registry Mirror & API Server
TeamSparkAI/mcp-registry
Mirror e API do MCP Registry com validação, explorador web e ferramentas de desenvolvimento
Ver no GitHubImplementação TypeScript do Registry oficial do Model Context Protocol, oferecendo um explorador web, API REST completa, validador de schemas e ferramentas de linting para servidores MCP. Funciona como monorepo com pacotes reutilizáveis e sincronização automática diária do registro oficial.
Instalação
npx convez-ai TeamSparkAI/mcp-registry1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Explorar e descobrir servidores MCP disponíveis
- Validar e lintar arquivos server.json antes de publicação
- Gerar configurações de cliente MCP customizadas
- Integrar funcionalidades de registry em suas próprias aplicações via pacotes npm
Veredito

Projeto maduro e bem-arquitetado que resolve o problema real de descoberta e validação no ecossistema MCP. A separação em pacotes reutilizáveis (validator, server API) torna-o valioso tanto para usuários finais quanto para desenvolvedores que querem integrar registry em seus próprios sistemas.
README
A tradução para o português deste README ainda está na fila.
MCP Registry Mirror & API Server
A TypeScript implementation of the Model Context Protocol Registry, providing:
- Registry Mirror Application - Next.js web app deployed on Vercel
- Reusable API Server Package - npm package for adding registry functionality to your own apps
- Validation Tools - Schema validation and linting for server.json files
🚀 Live Application
https://registry.teamspark.ai/
Features
- Registry Explorer - Browse and search MCP servers from the official registry
- Server Details - View full metadata, packages, and configuration options
- Configuration Generator - Generate MCP client configs with custom settings
- Server.json Tester - Validate and lint server.json files
- API Access - Full REST API at
/api/v0/*endpoints
📦 Packages
This monorepo contains reusable TypeScript packages:
mcp-registry-validator
Schema validation and linting for MCP server.json files. Works in both Node.js and browser environments.
Key Features:
- Multi-version schema support with automatic version detection
- Comprehensive linting rules for best practices
- Detailed error messages with JSON path references
- CLI tool and programmatic API
→ Installation, Usage & Rule Reference
mcp-registry-server
Core API server implementing the MCP Registry Protocol. The protocol implementation is completely independent of both the web framework and data storage mechanism.
Three-Layer Architecture:
- Protocol Core: Framework-agnostic service (no HTTP/framework dependencies)
- Data Sources: Pluggable interface - file, database, HTTP, custom
- Framework Adapters: Thin wrappers - Next.js, Express, etc.
This separation enables the same protocol implementation to work across all frameworks and storage options.
→ Installation, Usage & API Reference
🏗️ Architecture
Data Flow
Official Registry (GitHub)
↓ (daily sync via GHA)
server-registry.json
↓ (loaded by FileDataSource)
In-Memory Cache
↓ (served by RegistryService)
API Endpoints
↓ (consumed by frontend)
Next.js Application
Key Design Principles
- Frontend is 100% API-based - No direct file access from client
- Pluggable data sources - Swap FileDataSource for database, gateway, etc.
- Server-side validation - Schemas bundled at build time
- Serverless-ready - Works on Vercel, AWS Lambda, etc.
🔄 Automated Updates
A GitHub Action runs daily to:
- Download latest
server-registry.jsonfrom official registry - Sync schema versions from
modelcontextprotocol/static - Commit changes and trigger deployment
See .github/workflows/download-registry.yml
🛠️ Development
Prerequisites
- Node.js 18+
- pnpm 10+
Setup
# Install dependencies
pnpm install
# Build packages
pnpm --filter mcp-registry-validator build
pnpm --filter mcp-registry-server build
# Run dev server
pnpm run dev
Local API Testing
By default, the app uses the external registry at https://registry.teamspark.ai/api/v0. To test against the local API server instead, create a .env.local file:
# .env.local
NEXT_PUBLIC_REGISTRY_URL=/api/v0
This allows you to:
- Test API changes locally before deploying
- Validate the local API implementation
- Develop against local data without external dependencies
Without this variable, the app uses the default external registry (useful for testing the UX package integration).
Project Structure
/app # Next.js application
/api # API routes
/components # React components
/servers/[serverId]/[versionId] # Dynamic server detail pages
/packages
/mcp-registry-validator # Validation package
/mcp-registry-server # API server package
/registry # Protocol references
/schema # JSON schemas (versioned)
openapi.yaml # API specification
/public
server-registry.json # Registry data (synced daily)
Testing
# Run the validator
cd packages/mcp-registry-validator
pnpm dev validate path/to/server.json
# Test API endpoints
curl 'http://localhost:3000/api/v0/servers?limit=5'
curl 'http://localhost:3000/api/v0/servers/{serverId}/versions'
# Validate the entire registry
pnpm run registry:validate
📚 Documentation
- Deployment Guide - Deployment configuration and automated updates
- Registry Reference - OpenAPI spec and schema management
- Official Protocol - MCP Registry protocol specification
🎯 Current Status
Production Deployment: https://registry.teamspark.ai/
✅ What's Built
- Registry mirror application with API and web UI
mcp-registry-validator- Schema validation and linting packagemcp-registry-server- Core API server with Next.js adapter- Server-side validation endpoints
- Automated daily data and schema syncing
- Production deployment with in-memory caching
See docs/deployment.md for deployment details and todo.md for future enhancement ideas.
🤝 Contributing
This is an alternative TypeScript implementation of the official MCP Registry protocol. For protocol discussions and issues, see the official registry project.
📄 License
MIT