Daily MCP Registry Digest — 2026-03-21

by

Overview

  • Total updated servers: 8 (new latest versions or newly published entries within this dataset)
  • Deprecated servers: None observed
  • Deleted servers: None observed

Notable changes

  • New server: ai.aarna/atars-mcp (v0.1.0) published; crypto market signals/indicators/sentiment endpoint at https://mcp.aarna.ai/mcp.
  • Google Ads (Adramp) patch train + transport change: ai.adramp/google-ads advanced to v1.0.3. Earlier versions used sse (/sse); current latest uses streamable-http at https://mcp.adramp.ai and adds a public website URL (https://adramp.ai).
  • Perplexity API Platform update: ai.perplexity/mcp-server updated to v0.8.4 (npm stdio package).
  • TheProtocol added: cloud.theprotocol/registry published (v1.0.0) over SSE at https://api.theprotocol.cloud/mcp/sse; positioned as an A2A v1.0 sovereign agent platform with discovery/transfer/staking/governance tooling.
  • Meta Ads automation continued rapid updates: co.pipeboard/meta-ads-mcp latest is now v1.0.60 (long sequence of prior versions indicates frequent changes).
  • Investment tools daily-version cadence: app.marketgenius/mcp latest is 2026-03-19, following a date-stamped release pattern.
  • AdAdvisor patch update: ai.adadvisor/mcp-server latest is v1.0.1 (remote https://api.adadvisor.ai/mcp; auth header required).
  • Transport/endpoint moves worth flagging: ai.openmandate/mcphttps://api.openmandate.ai/mcp to https://mcp.openmandate.ai/mcp (latest v0.5.1 in dataset). Also ai.urlcheck/urlcheck-mcphttps://urlcheck.ai/mcp, while ai.preclick/preclick-mcphttps://preclick.ai/mcp.

Why it matters for operators

  • Transport changes impact connectivity and policy: Moves from SSE endpoints to streamable HTTP (e.g., Adramp) can change proxy compatibility, idle timeouts, observability patterns, and client configuration.
  • Endpoint churn requires allowlist/DNS review: Endpoint migrations (e.g., OpenMandate) and dual-branded/security services (URLCheck → PreClick) can break integrations if firewalls, egress allowlists, or secrets management are tied to old hostnames.
  • Rapid patch trains increase upgrade pressure: Highly frequently updated servers (e.g., Pipeboard Meta Ads, Marketgenius date versions) should be pinned and rolled forward via controlled deployment to avoid surprise behavior changes.
  • Auth requirements remain common: Several updated/active entries require bearer tokens via headers; operators should ensure secrets injection and rotation workflows are standardized across MCP clients.

Leave a Comment