Daily MCP Registry Digest

Summary

Total updated servers: 11 (servers showing multiple versions and/or recent updatedAt/statusChangedAt entries in this dataset).
Deprecated or deleted servers: None observed (all listed entries are status: active; no deprecation markers and no deletions included in the provided data).

co.pipeboard/meta-ads-mcp advanced through frequent patch releases, now 1.0.54 (latest). Operationally notable for fast-moving upstream behavior.
com.apify/apify-mcp-server updated to 0.9.8 (latest), continuing a rapid 0.9.x cadence.
com.b2bware/mcp-server progressed from 1.0.0 to 1.1.1 (latest) in quick succession.
ai.obris/mcp moved from 0.2.x through 0.3.0 to 0.4.0 (latest), indicating potentially meaningful behavior changes beyond simple patches.
ai.openmandate/mcp jumped from 0.3.x to 0.5.0 (latest) and standardized on https://mcp.openmandate.ai/mcp for newer entries.
ai.marketcore/mcp now latest as 1.0.2 with added/filled metadata (title/website/icons), which can affect catalog display and operator policy rules based on metadata.
ai.rolli/mcp updated to 1.1.6 (latest), including an environment-variable contract change: ROLLI_USER_ID becomes optional with a default.
ai.adadvisor/mcp-server patched to 1.0.1 (latest) with documentation URL updates (tracking/paths changed). No runtime endpoint change indicated.
ai.social-api/socialapi advanced to 1.0.1 (latest) after multiple close-together publishes; packaging remains mcp-socialapi@1.0.1 stdio.
com.compoid/mcp-server moved to 1.0.2 (latest) and added a public repository URL—useful for supply-chain review and pinning.
co.valid/chat-with-your-ads patched to 1.0.1 (latest) with minor icon/metadata adjustments.

Version churn drives pinning and rollout discipline: Several servers are releasing multiple versions within days. Operators should pin exact versions (npm/pypi/OCI) and promote via staged environments rather than tracking “latest”.
Endpoint drift can break allowlists and egress controls: Some servers show host/URL changes across versions (notably OpenMandate’s earlier api.* vs mcp.*). Validate DNS/host allowlists, TLS inspection policies, and outbound firewall rules when upgrading.
Config contract changes affect automation: Environment variable requirements changed in at least one popular server (Rolli’s user ID now optional). Update templating, secrets management, and validation to avoid failing strict config checks (or missing expected identity fields downstream).
Supply-chain posture improves when repos are added: New repository links (e.g., Compoid) enable code review, provenance checks, SBOM generation, and better vendor risk assessment.