Daily MCP Registry Digest

Daily MCP Registry Digest (2026-03-20)

ai.adadvisor/mcp-server → 1.0.1 (docs/website URL and auth header guidance updated)
ai.cookiy/cookiy → 1.7.9 (multiple rapid releases; latest consolidates prior changes)
ai.kawacode/mcp → 5.0.4 (notable: prior 5.0.3 entry showed a package/version mismatch; 5.0.4 aligns package version)
ai.marketcore/mcp → 1.0.2 (branding/title + website/icon additions; streamable-http + SSE retained)
ai.mcpcap/mcpcap → 0.9.6 (rapid pypi releases from 0.6.4→0.9.6)
ai.obris/mcp → 0.4.0 (incremental release line 0.2.5→0.4.0)
ai.openmandate/mcp → 0.5.1 (endpoint moved to https://mcp.openmandate.ai/mcp earlier; ensure clients are on current host)
ai.rolli/mcp → 1.1.7 (env var guidance: ROLLI_USER_ID now optional with default)
ai.social-api/socialapi → 1.0.1 (versioning stabilized after multiple close publishes)
app.himalayas/mcp → 1.0.2 (added SSE alongside streamable-http; description expanded to include posting jobs/talent)
app.marketgenius/mcp → 2026-03-19 (date-versioned rapid updates: 2026-03-15→18→19)
co.pipeboard/meta-ads-mcp → 1.0.60 (high-frequency patch line up to 1.0.60)
com.advisorfinder/mcp → 1.1.5 (rapid pypi patches 1.1.2→1.1.5)

Endpoint/hostname changes: OpenMandate moved to mcp.openmandate.ai vs earlier api.openmandate.ai. Operators should verify allowlists, egress policies, and health checks target the current base URL.
Transport surface expansion: Himalayas added SSE in addition to streamable-http, increasing compatibility with clients expecting event streams.
Package metadata consistency: Kawa Code had an intermediate entry where the npm package version did not match the server version; the latest (5.0.4) appears aligned—important for reproducible deployments.
High-churn services: Pipeboard Meta Ads (1.0.46→1.0.60), mcpcap (0.6.4→0.9.6), Cookiy (1.7.5→1.7.9), and AdvisorFinder (1.1.2→1.1.5) indicate fast iteration; expect more frequent upgrade/validation cycles.

Reduce breakage from endpoint drift: Hostname and path changes can silently fail behind strict outbound firewalling or pinned base URLs—update routing, DNS monitoring, and synthetic checks.
Pin versions and verify supply chain: With rapid releases, lock to known-good versions (npm/pypi) and validate that registry “server version” matches installed package versions in CI/CD.
Plan for transport differences: Adding SSE changes connection behavior (long-lived streams, proxy timeouts, idle handling). Ensure reverse proxies and load balancers are tuned accordingly.
Operational cadence: High-frequency publishers may require automated regression tests and staged rollouts to avoid production incidents from frequent patch updates.