Daily MCP Registry Digest — 2026-03-15

by

Summary

Total updated servers: 24 (servers with a newer “latest” release present in this registry slice).
Deprecated or deleted servers: None indicated (all entries shown are status: active; no deprecation/delete markers in provided data).

Notable changes

  • Pipeboard Meta Ads (co.pipeboard/meta-ads-mcp) continued rapid patch releases, now at 1.0.57 (latest). Operators should expect frequent updates and monitor for behavioral/tooling changes even in patch bumps.
  • Apify MCP Server (com.apify/apify-mcp-server) updated to 0.9.11 (latest) from 0.9.10.
  • OpenMandate (ai.openmandate/mcp) jumped to 0.5.0 (latest) from 0.3.x and standardized on https://mcp.openmandate.ai/mcp (earlier versions used https://api.openmandate.ai/mcp).
  • Obris (ai.obris/mcp) advanced through multiple versions to 0.4.0 (latest). If you pin versions, review changelogs before rolling forward.
  • AdvisorFinder (com.advisorfinder/mcp) moved forward to 1.1.5 (latest) from 1.1.2; repository reference also changes across versions (operators relying on source links should verify).
  • Rolli (ai.rolli/mcp) updated to 1.1.7 (latest). Notably, ROLLI_USER_ID is now optional with a default, reducing required config.
  • B2Bware (com.b2bware/mcp-server) updated to 1.1.1 (latest) from 1.0.0; both Streamable HTTP and SSE endpoints remain available.
  • Himalayas (app.himalayas/mcp) updated to 1.0.2 (latest) and added SSE alongside Streamable HTTP. Useful for operators standardizing on SSE for evented/streaming workflows.
  • MarketCore (ai.marketcore/mcp) reached 1.0.2 (latest) and added website/icon metadata across releases—no endpoint change but improved registry fidelity for discovery/UX.
  • URLCheck → PreClick rebrand: ai.urlcheck/urlcheck-mcp is labeled “formerly URLCheck” but remains status: active. A separate ai.preclick/preclick-mcp entry also exists, indicating naming consolidation in progress; watch for future deprecation of legacy hostname (urlcheck.ai).

Why it matters for operators

  • Endpoint drift and DNS changes: OpenMandate’s move from api.* to mcp.* is the kind of change that breaks allowlists, egress policies, and cached base URLs. Review network policies and connection configs.
  • High-churn services require pinning and rollout policy: Servers with frequent patch releases (e.g., Pipeboard) benefit from version pinning, staged rollouts, and automated health checks to avoid silent regressions.
  • Transport support impacts client architecture: Additions like SSE (Himalayas, B2Bware) can improve latency/streaming UX but may require proxy/timeouts tuning and different connection handling.
  • Metadata improvements reduce operational toil: Better icons/website URLs and clearer auth variable descriptions lower setup errors and make registry-driven discovery more reliable in internal catalogs.
  • Rebrands/duplication can create integration ambiguity: The coexistence of URLCheck/PreClick entries increases the risk of integrating the “wrong” endpoint. Standardize on the latest entry and document the canonical server name in your platform.

Leave a Comment