Daily MCP Registry Digest — 2026-03-04

by

Daily MCP Registry Digest (2026-03-04)

Updated servers (latest version changes)

Total updated servers: 11

  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (website/docs URL updated; auth header guidance link updated)
  • ai.obris/mcp: 0.2.5 → 0.2.6 (patch release)
  • app.himalayas/mcp: 1.0.0 → 1.0.2 (adds SSE remote alongside streamable HTTP; expanded description/metadata)
  • co.pipeboard/meta-ads-mcp: 1.0.48 → 1.0.49 (patch release)
  • com.apify/apify-mcp-server: 0.9.3 → 0.9.6 (multiple rapid patch releases)
  • com.civic/nexus: 0.1.105 → 0.1.106 (patch release)
  • com.linkbreakers/mcp: 1.26.3 → 1.27.0 (minor bump)
  • com.senzing/mcp: 0.13.1 → 0.13.3 (multiple patch releases)
  • com.solonai/grantai: 1.8.5 → 1.8.6 (distribution expanded: adds MCPB binaries while keeping OCI image)
  • com.teamwork/mcp: 1.10.4 → 1.10.5 (patch release)
  • com.worldairfares/flights-mcp: 1.0.0 → 1.0.1 (breaking-risk: remote URL changed from /mcp to root domain)

Deprecated or deleted servers

None observed in the provided registry slice (no entries marked deprecated; no removals detectable from this snapshot alone).

Notable changes

  • Endpoint/transport changes:
    • Himalayas adds SSE remote in addition to streamable HTTP.
    • World Airfares changes the remote base URL (clients pinned to the old path may fail).
  • Packaging/distribution expansion: GrantAi adds MCPB artifacts (macOS arm64, linux x64), which can simplify controlled installs vs. container-only workflows.
  • High-velocity patch trains: Apify, Senzing, and Teamwork show quick successive releases, increasing the odds of drift between pinned and latest deployments.

Why it matters for operators

  • Prevent breakage from endpoint drift: World Airfares’ URL change is the type of update that can silently break production agents if allowlists/firewalls or client configs are path-specific.
  • Transport support affects runtime behavior: SSE availability (Himalayas) can change connection lifecycles, proxy requirements, and observability patterns vs. standard HTTP request/response.
  • Release cadence impacts pinning policy: Rapid patch sequences (Apify/Senzing/Teamwork) favor automated update checks, canary rollouts, and explicit version pinning (especially for stdio-packaged servers).
  • Artifact choice affects supply chain and rollout: New MCPB binaries (GrantAi) can improve reproducibility and speed of rollout, but may require new verification steps (hash/cosign policy) alongside existing OCI flows.

Leave a Comment