Daily MCP Registry Digest (2026-03-28)

by

Summary

  • Total updated servers (new latest versions in this dataset): 10
  • Deprecated servers: None indicated (no status=deprecated observed)
  • Deleted servers: None indicated

Updated servers (latest version bumps)

  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (latest). Docs/website URL and auth header guidance refreshed.
  • ai.adramp/google-ads: 1.0.0 → 1.0.1 → 1.0.2 → 1.0.3 (latest). Transport moved from SSE to streamable-http; websiteUrl added.
  • ai.cookiy/cookiy: 1.7.5 → 1.7.6 → 1.7.7 → 1.7.9 (latest). Repository and developer portal references stabilized in later entries.
  • ai.kawacode/mcp: 5.0.2 → 5.0.3 → 5.0.4 (latest). Packaging metadata corrected (npm package version aligned to 5.0.4 in latest); website moved to kawacode.ai.
  • ai.marketcore/mcp: 1.0.0 → 1.0.1 → 1.0.2 (latest). Added icons/websiteUrl and title normalization (“MarketCore”).
  • ai.mcpanalytics/analytics: 1.0.4 → 1.0.5 (latest). Incremental release on same remote endpoint.
  • ai.mcpcap/mcpcap: 0.6.4 → 0.7.0 → 0.8.0 → 0.9.0 → 0.9.1 → 0.9.2 → 0.9.6 (latest). Rapid iteration; PyPI stdio package updated repeatedly.
  • ai.namewhisper/ens-tools: 1.0.0 → 1.0.1 → 1.0.2 (latest). Description expanded (includes register/manage wording).
  • ai.openmandate/mcp: 0.3.1 → 0.3.2 → 0.3.3 → 0.5.0 → 0.5.1 (latest). Remote base URL migrated to mcp.openmandate.ai; capability description updated (mandates/matching).
  • ai.perplexity/mcp-server: 0.8.3 → 0.8.4 → 0.9.0 (latest). Major/minor upgrade for the npm stdio server package.
  • ai.rolli/mcp: 1.1.4 → 1.1.5 → 1.1.6 → 1.1.7 (latest). Environment variable requirement relaxed (ROLLI_USER_ID becomes optional/defaulted).
  • ai.simstim/mcp: 1.0.0 → 1.0.1 (latest). Description/title refined; same remote base URL.
  • ai.thinkneo/control-plane: 1.0.0 → 1.0.1 → 1.0.2 (latest). Added title/websiteUrl; governance positioning clarified.
  • ai.trendsmcp/trends: 1.0.0 → 1.0.1 (latest). Introduced required Authorization bearer header.
  • app.cardog/mcp: 1.0.0 → 1.0.1 (latest). No functional transport change; version bump on same URL template.
  • app.himalayas/mcp: 1.0.0 → 1.0.1 → 1.0.2 (latest). Added SSE remote alongside streamable-http; description expanded to include posting jobs.
  • bot.402/discovery-oracle: 1.0.0-beta → 1.0.1-beta (latest). Description expanded (ranked endpoints, telemetry) on same remote.

Notable changes to watch

  • Transport/endpoint shifts: Adramp moved from SSE to streamable-http; Himalayas added SSE in addition to streamable-http. These can break clients pinned to specific transports or URLs.
  • New/clarified authentication requirements: Trends MCP now requires an Authorization bearer token; multiple services include strict bearer token headers (operators should ensure secret injection and rotation paths are correct).
  • Fast release cadence signals churn: mcpcap (0.6.4→0.9.6) and several others show rapid iteration, increasing the likelihood of behavioral changes even in minor/patch bumps.

Why it matters for operators

  • Prevent runtime failures: Changes in transport (SSE vs streamable-http) and remote base URLs can cause immediate connection errors if clients are hardcoded.
  • Secrets management and compliance: Newly-required headers (e.g., Trends Authorization) and clarified bearer formats mean you may need to update secret stores, templates, and audit policies.
  • Upgrade policy/compat testing: High-velocity projects (e.g., mcpcap) benefit from pinning versions and running automated smoke tests before promoting updates to production agents.

Leave a Comment