Daily MCP Registry Digest — 2026-03-23

by

Overview

  • Total updated servers (new latest version published): 10
  • Deprecated servers: 0
  • Deleted servers: 0

Updated servers (latest version changes)

  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (docs/website URL updated; auth header guidance updated).
  • ai.adramp/google-ads: 1.0.0 → 1.0.3 (transport moved from SSE to streamable HTTP; website URL added).
  • ai.cookiy/cookiy: 1.7.5 → 1.7.9 (metadata and developer portal alignment across rapid releases).
  • ai.kawacode/mcp: 5.0.2 → 5.0.4 (website URL updated; intermediate 5.0.3 shows a package version mismatch that is corrected in 5.0.4).
  • ai.marketcore/mcp: 1.0.0 → 1.0.2 (server title rebranded to “MarketCore”; website URL and icons added).
  • ai.mcpcap/mcpcap: 0.6.4 → 0.9.6 (multiple rapid PyPI releases; latest is 0.9.6).
  • ai.obris/mcp: 0.2.5 → 0.4.0 (continued incremental releases; packaging and remote endpoint remain consistent).
  • ai.openmandate/mcp: 0.3.1 → 0.5.1 (service matured; remote host stabilized at mcp.openmandate.ai).
  • ai.perplexity/mcp-server: 0.8.3 → 0.8.4 (npm package bump).
  • ai.trendsmcp/trends: 1.0.0 → 1.0.1 (now requires Authorization bearer token header; previously unauthenticated).
  • app.cardog/mcp: 1.0.0 → 1.0.1 (version bump; API-key variable-based remote URLs unchanged).
  • app.himalayas/mcp: 1.0.0 → 1.0.2 (adds/retains SSE option alongside streamable HTTP; expanded capability description).
  • app.marketgenius/mcp: 2026-03-15 → 2026-03-22 (frequent dated releases; endpoint unchanged).
  • bot.402/discovery-oracle: 1.0.0-beta → 1.0.1-beta (description updated to emphasize ranking/trust/payment telemetry).
  • church.ai.mcp/mcp-hub: 0.1.0 → 0.2.0 (clearer Telegram positioning and scope).
  • ai.rolli/mcp: 1.1.4 → 1.1.7 (ROLLI_USER_ID made optional with default behavior documented).
  • ai.social-api/socialapi: 0.1.0/1.0.0 → 1.0.1 (metadata cleanup; website URL present on latest; package identifier stays at mcp-socialapi@1.0.1).
  • co.pipeboard/meta-ads-mcp: 1.0.46 → 1.0.53 (many incremental releases; remote unchanged).

Notable changes to watch

  • Transport migration (SSE → streamable HTTP): Adramp Google Ads moves away from SSE (1.0.0) to streamable HTTP (1.0.1+). Operators should ensure client transport configuration matches the latest remote type.
  • Auth requirements tightened/clarified: Trends MCP 1.0.1 introduces a required Authorization bearer token header. Several services also updated documentation URLs and header guidance (e.g., AdAdvisor).
  • Rapid-release servers: mcpcap, pipeboard meta-ads, and marketgenius show high release cadence. This raises the need for pinning and staged rollout to avoid unexpected behavior changes.
  • Metadata consistency issues surfaced then corrected: Kawa Code 5.0.3 advertises @kawacode/mcp version 5.0.2 (package mismatch) while 5.0.4 aligns correctly—operators should prefer 5.0.4.

Why it matters for operators

  • Client compatibility and incident avoidance: Transport-type changes (SSE vs streamable HTTP) and new auth requirements can break integrations silently if configs are not updated.
  • Security posture: Newly required API keys (e.g., Trends MCP) shift services from open access to authenticated usage—update secret management, rotation, and least-privilege controls.
  • Release management: High-frequency versioning (particularly for security/network analysis and ads automation) increases risk of regressions; implement pinning, canary deployments, and automated smoke tests against MCP endpoints.
  • Registry hygiene: No deprecations/deletions detected in this dataset, but several projects shipped multiple intermediate versions quickly—monitor “latest” flags rather than assuming monotonic stability.

Leave a Comment