mcp-registry

> The missing discovery layer for Model Context Protocol servers.

Problem: MCP is growing fast but finding servers is chaos. There's no canonical registry, no search, no compatibility metadata — just scattered GitHub repos and random awesome-lists.

Solution: A community-maintained, searchable registry with structured metadata for every MCP server.

• registry/ — Structured JSON entries for each MCP server
• schema/ — JSON schema for registry entries
• web/ — Static site for browsing/searching (no backend needed)
• scripts/ — Validation and build tools

{
  "id": "sqlite-mcp",
  "name": "SQLite MCP Server",
  "description": "Read/write SQLite databases from any MCP-compatible agent",
  "author": "someone",
  "repo": "https://github.com/someone/sqlite-mcp",
  "install": "npx sqlite-mcp",
  "protocol_version": "2024-11-05",
  "tools": ["query", "execute", "list_tables", "describe_table"],
  "prompts": [],
  "resources": ["sqlite:///{path}"],
  "tags": ["database", "sqlite", "storage"],
  "verified": false,
  "submitted": "2026-03-22"
}

MCP is becoming the standard way for AI agents to access tools. But right now:

• Finding servers requires hours of GitHub searching
• No way to know if a server is maintained or abandoned
• No compatibility metadata (which clients work with it?)
• No usage stats or community validation

This registry changes that.

Submit a PR adding your server to registry/. One JSON file per server. The schema validates automatically.

🟡 Early — seeding initial entries. PRs welcome.

• Machina Market — Premium MCP server packs (catalog.json for agent-native purchase)
• MCP Spec
• MCP SDK