Daily MCP Registry Digest — 2026-03-05

Overview

  • Total updated servers (new latest versions observed): 12
  • Deprecated servers: None observed in provided data
  • Deleted servers: None observed in provided data

Updated servers (latest version now)

  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (docs/website URL and auth header guidance updated)
  • ai.marketcore/mcp: 1.0.0/1.0.1 → 1.0.2 (adds websiteUrl, title change to “MarketCore”, icon)
  • ai.obris/mcp: 0.2.5 → 0.2.6 (package version bump)
  • app.himalayas/mcp: 1.0.0/1.0.1 → 1.0.2 (adds SSE remote; description expands to include posting jobs)
  • co.pipeboard/meta-ads-mcp: 1.0.49 → 1.0.50 (rapid patch cadence continues)
  • com.apify/apify-mcp-server: 0.9.6 → 0.9.7 (rapid patch cadence continues)
  • com.boostedchat/travel: 0.1.1 → 0.1.2 (adds PyPI package alongside npm; server version bumps while package versions remain 0.1.1)
  • com.civic/nexus: 0.1.106 → 0.1.107 (patch bump)
  • com.fourmemeclaw/kuro-mcp: 1.0.0 → 1.1.0 (capability description tightened; adds icon)
  • com.linkbreakers/mcp: 1.27.0 → 1.28.0 (rapid patch/minor cadence continues)
  • com.microsoft/azure: 2.0.0-beta.23 → 2.0.0-beta.24 (new artifacts across npm/nuget/pypi and platform MCPB binaries)
  • com.senzing/mcp: 0.13.1 → 0.14.3 (multiple releases in short window; latest is 0.14.3)
  • com.shipstatic/mcp: 0.1.2 → 0.1.9 (multiple releases same day; latest is 0.1.9)

Notable changes

  • Transport surface expansion: Himalayas adds an SSE endpoint in addition to streamable-http, impacting client transport selection and egress policy.
  • High-churn publishers: Senzing, Shipstatic, Apify, Pipeboard, Linkbreakers show fast release sequences—expect frequent updates and potential behavioral drift even on patch/minor bumps.
  • Packaging/metadata shifts: BoostedTravel adds PyPI distribution; MarketCore adds branding assets and website URL; AdAdvisor updates documentation links and header guidance.
  • Data slice caveat: This page ends at com.smartbear/smartbear-mcp:0.14.0 with nextCursor set, so additional changes may exist beyond the provided window.

Why it matters for operators

  • Upgrade policy: With multiple servers releasing several times per day, pin versions (or MCPB/NPM/PyPI artifacts) and roll forward on a controlled cadence with smoke tests.
  • Transport and firewalling: New SSE endpoints can change long-lived connection behavior and network requirements; validate ingress/egress rules, timeouts, and proxy compatibility.
  • Auth/secret handling: Several entries include required bearer/API-key headers and env vars; re-check secret injection paths when versions update documentation or header formats.
  • Supply-chain hygiene: When server versions change without matching package version changes (e.g., BoostedTravel 0.1.2 server with 0.1.1 packages), verify which artifact your deployment actually consumes.

Leave a Comment