Daily MCP Registry Digest — 2026-03-08

by

Snapshot

  • Entries scanned: 100
  • Updated servers (new version observed in this dataset): 10
  • Deprecated servers: 0
  • Deleted servers: 0

Updated servers (high-signal changes)

  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (website/docs URL updated; latest now 1.0.1).
  • ai.marketcore/mcp: 1.0.0/1.0.1 → 1.0.2 (title/websiteUrl normalized; icon added earlier in 1.0.1 and carried forward; latest now 1.0.2).
  • ai.obris/mcp: 0.2.5 → 0.2.6 → 0.3.0 → 0.4.0 (rapid iteration; latest now 0.4.0; keep an eye on interface/behavior drift).
  • ai.openmandate/mcp: 0.3.1 → 0.3.2 → 0.3.3 (remote base URL shifted from https://api.openmandate.ai/mcp to https://mcp.openmandate.ai/mcp; description expanded; latest now 0.3.3).
  • ai.rolli/mcp: 1.1.4 → 1.1.5 → 1.1.6 (ROLLI_USER_ID made optional with default; latest now 1.1.6).
  • app.himalayas/mcp: 1.0.0 → 1.0.1 → 1.0.2 (added SSE remote alongside streamable-http; description expanded to include posting jobs; latest now 1.0.2).
  • co.pipeboard/meta-ads-mcp: 1.0.46 → … → 1.0.51 (multiple releases; latest now 1.0.51).
  • com.apify/apify-mcp-server: 0.9.3 → … → 0.9.7 (multiple releases; latest now 0.9.7).
  • com.civic/nexus: 0.1.104 → … → 0.1.109 (multiple releases; latest now 0.1.109).
  • com.microsoft/azure: 2.0.0-beta.23 → 2.0.0-beta.24 → 2.0.0-beta.25 (new beta build set across NuGet/npm/PyPI and platform-specific MCPB artifacts; latest now beta.25).

Other notable additions/active listings in this slice

  • Newly present (single version in this dataset; treat as “newly published” within this slice): AgentTrust (1.1.1), Fiber AI (1.0.0), ai.pictomancer/image-processing (0.1.0), unulu (0.1.0), bot.402/discovery-oracle (1.0.0-beta), Meet.bot (1.0.0), ContentFlow (1.0.0), DeepMap AI (2.0.0), LightSync Pro (2.8.1), Blockscout (0.15.0), Microsoft Fabric MCP (0.0.0-beta.9), Truncus (0.1.1), Fintrx (1.0.0), plus others.

Why it matters for operators

  • Endpoint changes can break connectivity: OpenMandate’s move to mcp.openmandate.ai is the clearest “action required” risk if you hardcode remote URLs or maintain allowlists.
  • Transport surface expansion affects network controls: Himalayas added an SSE remote in addition to streamable HTTP; MarketCore advertises both streamable-http and SSE. If you restrict egress, proxy protocols, or enforce per-transport policy, validate both paths.
  • Rapid version churn warrants pinning and staged rollouts: Obris, Apify, Civic Nexus, Pipeboard, and Azure beta releases show high cadence. Pin versions in production, test upgrades in staging, and monitor tool schemas/behavior for drift.
  • Credential handling remains a common source of failure: Multiple servers require Bearer/API keys via headers or env vars (AdAdvisor, OpenMandate, Apify, Meet.bot, etc.). Ensure secrets injection and rotation workflows are consistent across both stdio package installs and remote connections.

Leave a Comment