Daily MCP Registry Digest — 2026-03-07

by

Overview

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

Updated servers (high-signal changes)

  • ai.adadvisor/mcp-server 1.0.0 → 1.0.1: website/docs URL updated; Authorization header guidance updated to new docs path.
  • ai.marketcore/mcp 1.0.0/1.0.1 → 1.0.2: title/branding and websiteUrl added; icon added earlier; latest is 1.0.2.
  • ai.obris/mcp 0.2.5 → 0.2.6: patch release (PyPI package version bump).
  • ai.openmandate/mcp 0.3.1 → 0.3.2: remote base URL moved from https://api.openmandate.ai/mcp to https://mcp.openmandate.ai/mcp.
  • ai.rolli/mcp 1.1.4 → 1.1.6: env var semantics changed—ROLLI_USER_ID becomes optional with default; latest 1.1.6.
  • app.himalayas/mcp 1.0.0 → 1.0.2: capability expansion (description now includes “post jobs”); adds websiteUrl, icon, and SSE remote alongside streamable-http.
  • co.pipeboard/meta-ads-mcp 1.0.46 → 1.0.51: rapid patch train; latest 1.0.51.
  • com.apify/apify-mcp-server 0.9.3 → 0.9.7: incremental releases; latest 0.9.7.
  • com.civic/nexus 0.1.104 → 0.1.109: ongoing frequent updates; latest 0.1.109.
  • com.fourmemeclaw/kuro-mcp 1.0.0 → 1.1.0: description tightened/clarified; icon added.
  • com.microsoft/agent365-mailtools 1.0.0 → 1.0.1: remote URL changed from a fixed tenant GUID to templated {tenant_id} variable (operator-supplied) for multi-tenant deployment.
  • com.microsoft/azure 2.0.0-beta.23 → 2.0.0-beta.25: beta bump with refreshed artifacts and checksums across NuGet/npm/PyPI/mcpb.
  • com.olane/copass-local 0.3.1 → 0.3.2: patch release (PyPI package version bump).
  • com.boostedchat/travel 0.1.1 → 0.1.2: adds PyPI package distribution alongside npm; keeps same remote.
  • com.keboola/mcp 1.46.0 → 1.48.0: minor version jump (PyPI package); latest 1.48.0.
  • com.postman/postman-mcp-server 2.7.1 → 2.8.1 (not latest in snapshot metadata view flagged): new version published; same remote set, new mcpb artifacts and checksums.

Notable operator-impacting changes

  • Endpoint migrations: OpenMandate’s remote host changed; operators with allowlists, egress policies, or pinned URLs must update to avoid connectivity failures.
  • Auth/runtime parameterization: Microsoft Agent365 Mail Tools now requires a tenant_id variable in the URL; automation must inject the correct tenant at deployment time.
  • Transport surface area growth: Himalayas adds SSE alongside streamable-http; this can affect proxy configuration, idle timeouts, and observability.
  • Dependency/update velocity signals: Civic Nexus, Pipeboard Meta Ads, and Apify show fast release cadence; consider pinning versions and planning regular upgrade windows.

Why it matters for operators

  • Stability and change control: Host/URL changes and rapid patch trains can break production if you rely on static allowlists, cached configs, or pinned endpoints.
  • Security posture: Changes in auth guidance and URL templating often come with updated secret-handling or tenancy assumptions—verify secrets injection, rotation, and RBAC scopes after upgrades.
  • Network and platform readiness: Adding SSE or new artifact types (e.g., PyPI alongside npm) can impact runtime choices, container baselines, and egress controls.

Leave a Comment