Daily MCP Registry Digest — 2026-03-03

by

Daily MCP Registry Digest (2026-03-03)

Overview

  • Total updated servers: 9
  • Deprecated servers: none observed in provided data
  • Deleted servers: none observed in provided data

Updated servers (latest versions)

  • com.apify/apify-mcp-server: 0.9.3 → 0.9.5 (multiple same-day releases)
  • com.linkbreakers/mcp: 1.25.1 → 1.26.3 (high-frequency patch/minor train)
  • com.teamwork/mcp: 1.10.2 → 1.10.4
  • co.pipeboard/meta-ads-mcp: 1.0.46 → 1.0.48
  • app.himalayas/mcp: 1.0.0 → 1.0.2 (adds title/website/icons; includes SSE endpoint alongside streamable-http)
  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (website/docs URL and auth header help text updated)
  • ai.obris/mcp: 0.2.5 → 0.2.6
  • com.boostedchat/travel: 0.1.1 → 0.1.2 (adds PyPI package entry in addition to npm; version metadata not fully aligned across packages)
  • io.github.BigJai/codemunch-pro: 0.1.1 → 1.2.0 (capabilities text indicates tool-count increase: 13 → 15 tools)

Notable changes

  • Rapid release trains: Apify and Linkbreakers show multiple incremental releases; expect churn and potential breaking behavioral changes even when semver suggests “patch”.
  • Transport surface expansion: Himalayas now advertises both streamable-http and sse, which may affect client selection, proxying, and long-lived connection handling.
  • Packaging footprint changes: BoostedTravel adds a second distribution channel (PyPI). This can change how operators source/bundle the server in controlled environments.
  • Auth/header schema drift: AdAdvisor’s remote auth documentation and website entry changed (still Bearer-token based). SGP Directory (already at latest) demonstrates a stricter header template with variable substitution—watch for similar shifts elsewhere.

Why this matters for operators

  • Pin and promote: With fast-follow releases (notably Linkbreakers 1.25.1 → 1.26.3), pin exact versions and promote through staging to avoid surprise tool/behavior changes.
  • Validate transports: New/added SSE endpoints may require different timeout, load balancer, and observability settings compared to request/response HTTP.
  • Re-check secrets wiring: Even when endpoints stay stable, changes in header templates, variable naming, or docs often signal upcoming auth expectations—confirm your secret injection and rotation flows still match.
  • Supply-chain control: Added distribution methods (npm + PyPI, or new containers) expand the artifact set you must scan, mirror, and allowlist.

Leave a Comment