Daily MCP Registry Digest — 2026-03-13

by

Overview

  • Total updated servers (latest-version moves observed): 10
  • Deprecated servers: 0 flagged
  • Deleted servers: 0 flagged

Updated servers (latest now points to)

  • co.pipeboard/meta-ads-mcp → 1.0.55 (continued rapid release cadence)
  • com.apify/apify-mcp-server → 0.9.9 (multi-step patch train up to latest)
  • com.advisorfinder/mcp → 1.1.3
  • com.compoid/mcp-server → 1.0.3 (repo reference changed to GitLab)
  • com.b2bware/mcp-server → 1.1.1
  • com.codescene/codescene-mcp-server → 1.1.0
  • com.agialpha/agi-alpha → 1.0.0
  • com.aibooma/agent-registry → 0.2.0
  • com.dealsurface/dealsurface → 0.1.1
  • co.valid/chat-with-your-ads → 1.0.1

Notable changes

  • Endpoint and routing changes that may break allowlists:
    • ai.openmandate/mcp moved to https://mcp.openmandate.ai/mcp (latest 0.5.0), replacing earlier https://api.openmandate.ai/mcp.
    • ai.urlcheck/urlcheck-mcp is now branded as PreClick (“formerly URLCheck”) but still points at https://urlcheck.ai/mcp; separate dedicated PreClick entry exists at ai.preclick/preclick-mcp → https://preclick.ai/mcp.
    • ai.social-api/socialapi shows multiple close-in publishes; ensure you’re on latest (1.0.1) and not pinning older metadata.
  • Transport surface expansion:
    • app.himalayas/mcp and ai.marketcore/mcp advertise both streamable-http and sse endpoints, which impacts client runtime selection and proxy configuration.
  • Operator config ergonomics:
    • ai.rolli/mcp updated env var semantics: ROLLI_USER_ID becomes optional (defaults to rolli-mcp), reducing required secrets/config.
    • co.valid/chat-with-your-ads and ai.marketcore/mcp include icon metadata changes—mostly cosmetic, but can affect internal catalogs/portals that render registry icons.
    • com.compoid/mcp-server changed repository location across releases (GitHub → GitLab), which can affect supply-chain verification workflows and source-of-truth links.
  • High-churn release trains worth watching:
    • co.pipeboard/meta-ads-mcp progressed through many versions; latest is 1.0.55.
    • com.apify/apify-mcp-server advanced from 0.9.3 to 0.9.9 in the dataset window.
    • ai.obris/mcp jumped multiple minors (0.2.5 → 0.4.0), suggesting breaking/behavioral changes are plausible despite “active” status.

Why it matters for operators

  • Firewall/egress and allowlists: endpoint moves (e.g., OpenMandate) and dual endpoints (URLCheck vs PreClick) can cause unexpected connection failures if you pin hostnames.
  • Upgrade strategy: patch-train servers (Apify, Pipeboard, Compoid, B2Bware) benefit from version pinning + scheduled rollouts; treat “latest” as a moving target.
  • Auth and secret handling: many updates are metadata-only but still touch required headers/env vars; validate your secret injection paths when switching versions or transport.
  • Client compatibility: SSE vs streamable-http availability influences which MCP client libraries/proxies work out of the box; confirm your runtime supports the advertised transports.

Leave a Comment