
mcp-registry
A community-maintained registry of Model Context Protocol (MCP) servers with structured installation configurations for easy integration.
Performed an automated update for the tool enrichment statistics, including GitHub star counts and last-commit timestamps, to ensure the registry remains accurate and up-to-date. This routine maintenance helps provide users with the latest metadata on supported MCP tools across the platform. 
Ran the automated enrichment pipeline to refresh GitHub star counts and record the latest commit timestamps for supported projects in public/enrichment.json. This ensures metadata stays accurate for community tracking. 
Updated public/enrichment.json with the latest star counts and last-commit timestamps for all integrated servers. This automated maintenance ensures that visibility remains accurate across the platform without manual intervention. 
Increased the maximum allowed length for server descriptions from 200 characters to 400 characters to allow for more detailed documentation. Updated both the Zod schema and the README documentation to reflect this change and fixed the corresponding unit tests, which were failing due to the old validation threshold. 
We've added support for Commune MCP, offering specialized email infrastructure designed specifically for AI agents. Unlike standard integrations, it supports programmatic inbox provisioning, native thread tracking for concurrent tasks, and structured data output for received emails, streamlining agent-to-human interactions. You can get started easily using uvx to run the server. 
We've added support for the BGPT MCP server, allowing users to perform full-text scientific paper searches directly within their MCP-compatible environments. This integration provides access to structured experimental data from academic studies via both SSE and Streamable HTTP transports. It's a great way to streamline your research workflow with 50 free searches available out of the box. 
Added support for the IntoDNS.ai MCP server, enabling AI agents to perform DNS and email security scans directly using tools for SPF, DKIM, DMARC, DNSSEC, and more. This integration facilitates easier security auditing and deliverability checking for domains. 
We've added the IntoDNS.ai MCP server to our registry, allowing AI agents to perform automated DNS and email security checks. The server supports a wide range of protocols including SPF, DKIM, DMARC, and DNSSEC, providing reliable deliverability insights directly to your workflows. Keeping your DNS records healthy just got a whole lot easier. 
We've performed an automated update to public/enrichment.json to keep our project metrics current, including the latest GitHub star counts and last-commit timestamps. Keeping this metadata refreshed ensures that tools and dashboards relying on this registry provide accurate, up-to-date visibility into our ecosystem. 
The enrichment data in public/enrichment.json has been updated to reflect the latest GitHub stats and timestamps. Keeping this metadata current ensures that our tool discovery and integration logic remains accurate. 
The public/enrichment.json data has been automatically updated with the latest GitHub star counts and recent commit timestamps. This ensures that our service discovery and integration metadata remains accurate and current. 
The project's enrichment data, including repository star counts and last commit timestamps, has been automatically updated to reflect the latest upstream status. This ensures that metadata across our integrated services remains current. 
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.


