Daily MCP Registry Digest — 2026-03-24

by

Daily MCP Registry Digest (2026-03-24)

Overview

  • Total updated servers (latest version present in this dataset): 8
  • Deprecated servers: 0
  • Deleted servers: 0

Notable changes

  • AdAdvisor (ai.adadvisor/mcp-server): 1.0.0 → 1.0.1. Website/docs URL updated; Authorization header guidance updated. Remote endpoint remains https://api.adadvisor.ai/mcp.
  • Adramp Google Ads (ai.adramp/google-ads): 1.0.0 → 1.0.3. Transport shifted from sse to streamable-http (endpoint now https://mcp.adramp.ai); website URL added (https://adramp.ai).
  • Cookiy (ai.cookiy/cookiy): 1.7.5 → 1.7.9. Description/positioning refined; repository reference changed to the “cookiy-skill” repo; developer portal website URL consistently set.
  • Kawa Code MCP (ai.kawacode/mcp): 5.0.2 → 5.0.4. Website domain moved to kawacode.ai. Prior version 5.0.3 appears to have a package version mismatch (registry entry shows server 5.0.3 while npm package stayed at 5.0.2), corrected in 5.0.4.
  • MarketCore (ai.marketcore/mcp): 1.0.0 → 1.0.2. Title/branding normalized (now “MarketCore”); website URL added; icons added; both streamable-http and sse transports remain available.
  • mcpcap (ai.mcpcap/mcpcap): 0.6.4 → 0.9.6 (multiple rapid releases). Operators should expect behavior/CLI/tooling changes typical for a fast-moving 0.x line; current latest is PyPI mcpcap==0.9.6.
  • OpenMandate (ai.openmandate/mcp): 0.3.1 → 0.5.1. Remote base changed to https://mcp.openmandate.ai/mcp (from earlier api.openmandate.ai), indicating endpoint consolidation; Authorization (Bearer) remains required.
  • Rolli (ai.rolli/mcp): 1.1.4 → 1.1.7. Environment variable requirements relaxed/clarified (ROLLI_USER_ID now optional with a default), reducing config friction for stdio deployments.

Why it matters for operators

  • Transport changes can break clients: Adramp’s move from SSE to streamable HTTP may require client transport reconfiguration, firewall rules review, and health-check updates.
  • Endpoint migrations impact routing and allowlists: OpenMandate’s host change (api.* to mcp.*) can break DNS allowlists, proxy routes, and outbound egress policies if not updated.
  • Auth/header requirements affect secret management: Several services rely on Bearer tokens (AdAdvisor, OpenMandate) or optional keys (PreClick/URLCheck patterns in the dataset). Validate that secret injection and request middleware still match provider guidance.
  • Registry metadata correctness is operationally important: The Kawa Code package-version mismatch in 5.0.3 is the kind of drift that can confuse automated deploy/pin workflows; ensure you pin to the latest corrected entry (5.0.4).
  • Fast-moving 0.x packages warrant tighter change control: mcpcap’s rapid release cadence suggests operators should pin versions, stage upgrades, and run regression checks before rolling broadly.

Leave a Comment