Daily MCP Registry Digest

Overview

Total updated servers (latest version changes in this dataset): 6
Deprecated or deleted servers: None indicated (no registry status of deprecated/deleted present in the provided entries)

ai.adramp/google-ads → 1.0.3 (latest). Notable: earlier versions include an SSE remote; latest is streamable-http at https://mcp.adramp.ai and adds websiteUrl (https://adramp.ai).
ai.cookiy/cookiy → 1.7.9 (latest). Notable: description/repo metadata stabilized around the “cookiy-skill” repo and developer portal URL.
ai.kawacode/mcp → 5.0.4 (latest). Notable: earlier 5.0.3 entry had a package version mismatch (package still listed 5.0.2); latest aligns package version to 5.0.4 and standardizes websiteUrl to https://kawacode.ai.
ai.mcpcap/mcpcap → 0.9.6 (latest). Notable: rapid patch progression (0.6.4 → 0.9.6 in the provided history), indicating frequent changes for operators relying on deterministic behavior.
app.marketgenius/mcp → 2026-03-24 (latest). Notable: date-based versioning with frequent releases across consecutive days.
cloud.factry.portal/historian-mcp-server → 0.0.2 (latest). Notable: OCI image pin changed from docker.io/factry/mcp-server:latest (0.0.1) to docker.io/factry/mcp-server:0.0.2, improving deploy reproducibility.

Transport standardization and migration: Adramp Google Ads moved from an SSE endpoint (older version) to streamable HTTP in newer versions, reducing reliance on long-lived event streams.
Auth requirements tightening: Trends MCP 1.0.1 adds required Authorization bearer token header (where 1.0.0 did not show required auth in the entry), which can break existing unauthenticated integrations.
Release cadence signals: mcpcap and Marketgenius exhibit frequent increments; expect behavioral changes, bugfixes, and potential tool/contract drift if you auto-upgrade.
Packaging metadata hygiene: Kawa Code resolved package version mismatch, reducing confusion for npm-based deployments.

Upgrade planning: Transport changes (SSE → streamable HTTP) can require client configuration updates, connection handling changes, and different proxy/load balancer tuning.
Reliability and reproducibility: Pinning container images (Factry 0.0.2) is materially safer than deploying :latest; it supports rollbacks and reduces “unknown change” incidents.
Security posture: Newly required auth headers (e.g., Trends MCP) should trigger secrets management updates, header allowlists in gateways, and regression tests for 401/403 paths.
Change control: High-frequency releases increase the need for version pinning, staged rollouts, and contract tests to prevent tool schema drift from impacting automations.