Daily MCP Registry Digest — 2026-03-10

by

Summary

  • Total updated servers: 15 (servers with multiple versions listed and a clear latest version)
  • Deprecated servers: 0 detected
  • Deleted servers: 0 detected

Notable changes

  • ai.openmandate/mcp: 0.3.1 → 0.3.2 → 0.3.3 → 0.5.0 (latest). Also moved the remote from https://api.openmandate.ai/mcp to https://mcp.openmandate.ai/mcp (bearer auth remains). This is the most material operational change due to endpoint/hostname change.
  • ai.obris/mcp: 0.2.5 → 0.2.6 → 0.3.0 → 0.4.0 (latest). Both PyPI (stdio) and hosted remote remain present; update indicates ongoing capability/behavior changes worth validating in staged environments.
  • co.pipeboard/meta-ads-mcp: 1.0.46 → … → 1.0.52 (latest). Rapid patch cadence; expect tool/behavior tweaks even if transport/URL stays stable.
  • com.civic/nexus: 0.1.104 → … → 0.1.109 (latest). Frequent gateway updates; operators should watch for auth/workflow behavior changes even when the endpoint remains stable.
  • com.apify/apify-mcp-server: 0.9.3 → … → 0.9.7 (latest). Continuous updates; confirm compatibility with your token handling and any tool schemas you rely on.
  • church.ai.mcp/mcp-hub: 0.1.0 → 0.2.0 (latest). Expanded Telegram-focused positioning; endpoint unchanged.
  • ai.marketcore/mcp: 1.0.0 → 1.0.1 → 1.0.2 (latest). Adds icon/metadata and finalizes website URL; transports include streamable-http and SSE.
  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (latest). Primarily documentation/website URL and auth guidance refinement; remote endpoint unchanged.
  • app.himalayas/mcp: 1.0.0 → 1.0.1 → 1.0.2 (latest). Adds/clarifies SSE alongside streamable-http and expands capability wording (search + post jobs).
  • ai.rolli/mcp: 1.1.4 → 1.1.5 → 1.1.6 (latest). Makes ROLLI_USER_ID optional with a default; reduces required config surface for deployments.
  • com.boostedchat/travel: 0.1.1 → 0.1.2 (latest). Adds PyPI distribution alongside npm; note package version fields appear to lag (npm/pypi show 0.1.1) even though the server record is 0.1.2—operators should verify the actual artifact version being installed.
  • bot.402/discovery-oracle: 1.0.0-beta → 1.0.1-beta (latest). Description indicates expanded discovery/ranking/telemetry surfaces; endpoint unchanged.
  • com.linkbreakers/mcp: many versions up through 1.28.0 (latest shown in this snapshot). High-frequency releases; treat as change-prone and pin versions for stable production behavior.

Why it matters for operators

  • Endpoint changes can break clients: OpenMandate’s hostname move (api.* → mcp.*) is the key “update now” item for any hard-coded allowlists, egress rules, DNS pinning, or client configs.
  • High-cadence servers increase drift risk: Pipeboard, Civic Nexus, Apify, and Linkbreakers show frequent updates; pin versions for stdio package installs and add regression checks for hosted remotes to avoid silent behavior changes.
  • Transport expansion affects connectivity assumptions: Himalayas and MarketCore include SSE as an option; if your runtime prefers or blocks SSE/long-lived connections, validate network policy and timeouts.
  • Configuration surface changes reduce operational friction: Rolli making ROLLI_USER_ID optional can simplify secrets management and templated deployments.
  • Artifact/version mismatches need validation: BoostedTravel’s server version vs package version mismatch is a signal to verify what your installer pulls, and to lock to known-good versions in automation.

Leave a Comment