Daily MCP Registry Digest — 2026-03-31

by

Overview

  • Total updated servers (new latest versions observed): 10
  • Deprecated servers: none indicated in this data (all statuses are active)
  • Deleted servers: none indicated in this data

Updated servers (latest version now)

  • ai.adadvisor/mcp-server: 1.0.1 is latest (was 1.0.0)
  • ai.adramp/google-ads: 1.0.3 is latest (was 1.0.0–1.0.2)
  • ai.cookiy/cookiy: 1.7.19 is latest (multiple prior 1.7.x entries)
  • ai.inflowpay.app/inflow: 1.0.2 is latest (was 1.0.0–1.0.1 earlier today)
  • ai.kawacode/mcp: 5.0.4 is latest (was 5.0.2–5.0.3)
  • ai.mcpanalytics/analytics: 1.0.5 is latest (was 1.0.4)
  • ai.mcpcap/mcpcap: 0.9.6 is latest (was 0.6.4–0.9.2)
  • ai.namewhisper/ens-tools: 1.0.2 is latest (was 1.0.0–1.0.1)
  • ai.openmandate/mcp: 0.5.1 is latest (was 0.3.x and 0.5.0)
  • ai.preclick/preclick-mcp: 0.3.2 is latest (was 0.2.0)

Notable changes

  • Transport/endpoint shifts (breaking-change risk):
    • ai.adramp/google-ads moved from sse (1.0.0 at https://mcp.adramp.ai/sse) to streamable-http (1.0.1+ at https://mcp.adramp.ai).
    • ai.pictomancer/image-processing changed remote base URL from https://mcp.pictomancer.ai/mcp (0.1.0) to https://api.pictomancer.ai/mcp (0.2.0).
  • Rapid version churn in operator-sensitive domains:
    • ai.inflowpay.app/inflow released 1.0.0 → 1.0.1 → 1.0.2 in the same day window, suggesting fast iteration on an onboarding/payment/provisioning surface.
    • ai.mcpcap/mcpcap shows quick successive releases up to 0.9.6, implying frequent tool/behavior changes for a security/traffic analysis workflow.
  • Auth/header expectations tightened/standardized:
    • ai.adadvisor/mcp-server keeps a required Authorization: Bearer ... secret header; documentation URL changed between 1.0.0 and 1.0.1 (operators should ensure runbooks point to the new doc path).
    • ai.trendsmcp/trends earlier versions show a transition from no header to requiring Authorization bearer token; current latest (1.0.4) expects the bearer token header.
  • Naming/product metadata refinements:
    • ai.marketcore/mcp title/website/icon fields evolved across 1.0.0–1.0.2 (helpful for discovery, but also a signal that integrations relying on display metadata may change).
    • ai.urlcheck/urlcheck-mcp is branded as “PreClick … (formerly URLCheck)”, indicating consolidation/renaming while keeping the older server name/endpoint.

Why it matters for operators

  • Watch for transport and base-URL changes: SSE→streamable HTTP and host changes can break clients, proxies, and allowlists. Validate connectivity, timeouts, and streaming semantics before promoting updates.
  • Pin versions for stability: Several servers show fast release cadence (notably InFlow and mcpcap). Pin to known-good versions in production and promote via staged rollouts.
  • Re-audit auth handling: Multiple services require secret headers (Authorization bearer tokens, vendor API keys, or micropayment headers like X-PAYMENT). Confirm secrets injection, redaction in logs, and per-environment key rotation.
  • Update operational documentation: Several entries changed website/docs URLs and branding; keep internal runbooks aligned so on-call can find the right docs quickly.

Leave a Comment