
mcp-registry
A community-maintained registry of Model Context Protocol (MCP) servers with structured installation configurations for easy integration.
Updated the enrichment metadata, including repository star counts and last commit timestamps, for various integrations in the registry. Keeping this data current ensures that users have accurate information when browsing or selecting tools. 
Updated public/enrichment.json with the latest metadata for tracked services, ensuring that star counts and recent commit timestamps remain accurate. This periodic refresh keeps the dashboard data current and relevant for users browsing tracked registries. 
ravitemer pushed an automated update to the enrichment data on main. The commit refreshes public/enrichment.json with new lastUpdated timestamps and updated stars/lastCommit values across multiple servers (e.g., filesystem, github, context7, playwright, aws_docs, figma).
Ravitemer pushed an auto‐update to the main branch, refreshing public/enrichment.json with new star counts and lastCommit timestamps for all tracked servers (lastUpdated bumped to 1771398080). The update includes slight increases across the board—GitHub is now at 27,028 stars, Figma at 13,155, Playwright at 27,304, and so on—keeping our enrichment data current.
ravitemer pushed an automated update to enrichment.json on the main branch, bumping the “lastUpdated” timestamp and refreshing star counts and last-commit timestamps across multiple servers (e.g., GitHub to 27 000 stars, Playwright to 27 248). This keeps the enrichment data in sync with the latest metrics.
ravitemer pushed an automatic update to enrichment.json on main, refreshing the overall timestamp and bumping star counts and updatedAt fields across all servers. This change simply pulls in the latest metrics (stars and last commit times) without any manual edits.
ravitemer pushed an automatic update to public/enrichment.json on the main branch, refreshing star counts and lastCommit/updatedAt timestamps across all listed servers. This change keeps the enrichment data (stars, last commit times, and version info) up to date.
ravitemer pushed an automated update to public/enrichment.json on the main branch, refreshing the enrichment data (stars counts and lastCommit timestamps) across all listed servers and bumping the overall lastUpdated timestamp. This keeps the project’s metadata in sync with the latest GitHub stats.
ravitemer pushed an automated update to public/enrichment.json on main, bumping the lastUpdated timestamp and refreshing star counts and lastCommit entries for all listed servers. This change keeps the enrichment data in sync with the latest metrics.
ravitemer pushed an auto‐update to public/enrichment.json on the main branch, bumping the overall lastUpdated timestamp and refreshing star counts and lastCommit fields across multiple services. This change keeps our enrichment data (stars, lastCommit) current.
ravitemer pushed an automated update to public/enrichment.json on main, refreshing the overall lastUpdated timestamp as well as individual star counts, lastCommit and updatedAt fields for all listed servers. This routine commit ensures enrichment data stays current across the project’s integrations.
ravitemer pushed an automatic update to public/enrichment.json on main, bumping the overall lastUpdated timestamp and refreshing each server’s stars, lastCommit and updatedAt fields. The change keeps all service stats (filesystem, GitHub, context7, Stripe, Playwright, AWS docs, etc.) up to date with their latest counts.
ravitemer pushed an automated update to public/enrichment.json on the main branch, bumping the overall lastUpdated timestamp and refreshing star counts, lastCommit values and updatedAt fields for all listed servers. This includes specific lastCommit updates for apify and aws_docs along with slight star count increases across the board.
ravitemer pushed an auto‐update to the enrichment.json on main, bumping the overall lastUpdated timestamp and refreshing stars, lastCommit and updatedAt values for all tracked servers. This keeps our enrichment data in sync with the latest repository metrics.
ravitemer pushed an auto‐update to public/enrichment.json on main, bumping the overall lastUpdated timestamp and refreshing star counts and lastCommit timestamps for multiple servers. This commit keeps the enrichment data up-to-date with the latest stats.
ravitemer pushed an auto‐update to public/enrichment.json on main, refreshing star counts and lastCommit timestamps for numerous servers (e.g., filesystem, github, context7, stripe, playwright, aws_docs, etc.). All updatedAt fields were bumped to the new timestamp, keeping the enrichment data in sync.
ravitemer pushed an automated update to public/enrichment.json on the main branch, refreshing the overall lastUpdated timestamp and bumping star counts and lastCommit times for all listed servers. This keeps the enrichment data current with the latest GitHub stats.
ravitemer pushed an automatic update to public/enrichment.json on the main branch, bumping the overall lastUpdated timestamp and refreshing star counts and last-commit timestamps for all listed servers (e.g., filesystem, GitHub, browserbase, stripe, playwright, aws_docs, etc.). This commit keeps the enrichment data in sync with the latest metrics.
ravitemer pushed an automated update to public/enrichment.json on the main branch, bumping the overall lastUpdated timestamp and refreshing star counts and lastCommit timestamps for numerous servers (e.g., filesystem, GitHub, Stripe, AWS docs and more). This keeps the enrichment data in sync with the latest repository metrics.
ravitemer pushed an auto‐update to public/enrichment.json on the main branch, refreshing the “stars” counts and “lastCommit”/“updatedAt” timestamps across all servers. This commit bumps the overall lastUpdated timestamp to ensure the enrichment data reflects the latest metrics.