Daily MCP Registry Digest — 2026-03-17

by

Overview

  • Total updated servers (new latest versions detected): 13
  • Deprecated servers: 0
  • Deleted servers: 0

Updated servers (latest version changes)

  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (doc/website URL updated; auth header guidance updated)
  • ai.cookiy/cookiy: 1.7.5 → 1.7.6 (repo and website metadata updated; remote unchanged)
  • ai.marketcore/mcp: 1.0.0/1.0.1/1.0.2 → 1.0.2 latest (branding/title normalized to “MarketCore”; website + icons added)
  • ai.mcpcap/mcpcap: 0.6.4 → 0.7.0 → 0.8.0 (rapid pypi release train; latest now 0.8.0)
  • ai.obris/mcp: 0.2.5 → 0.2.6 → 0.3.0 → 0.4.0 (multiple version bumps; latest now 0.4.0)
  • ai.openmandate/mcp: 0.3.1 → 0.3.2 → 0.3.3 → 0.5.0 → 0.5.1 (endpoint moved to mcp.openmandate.ai; description matured)
  • ai.rolli/mcp: 1.1.4 → 1.1.5 → 1.1.6 → 1.1.7 (env var semantics clarified: ROLLI_USER_ID now optional with default)
  • ai.social-api/socialapi: 1.0.0 → 1.0.1 (version alignment; website metadata added)
  • app.himalayas/mcp: 1.0.0 → 1.0.1 → 1.0.2 (adds “post remote jobs” capability; adds SSE remote alongside HTTP)
  • bot.402/discovery-oracle: 1.0.0-beta → 1.0.1-beta (description expanded toward ranked endpoints + telemetry)
  • church.ai.mcp/mcp-hub: 0.1.0 → 0.2.0 (Telegram connector description expanded; still same remote URL)
  • co.valid/chat-with-your-ads: 1.0.0 → 1.0.1 (minor icon metadata change; same remote)
  • com.apify/apify-mcp-server: 0.9.10 → 0.9.11 (patch update; remote/auth unchanged)
  • com.b2bware/mcp-server: 1.0.0 → 1.1.0 → 1.1.1 (incremental releases; remotes unchanged)
  • com.advisorfinder/mcp: 1.1.2 → 1.1.3 → 1.1.4 → 1.1.5 (incremental releases; repo metadata stabilized)
  • com.agentictotem/web-extractor: 1.0.3 → 1.0.4 → 1.0.5 (patch update; icon ordering/metadata tweaks; remote unchanged)

Notable operator-impacting changes

  • Endpoint changes to watch: OpenMandate moved traffic to https://mcp.openmandate.ai/mcp (vs earlier api.openmandate.ai). If you enforce egress allowlists, policy-based routing, or per-host rate limits, update now.
  • New transport option (SSE): Himalayas Remote Jobs now advertises an SSE endpoint in addition to streamable HTTP. This can affect proxy config (timeouts, buffering, connection limits) and client capability negotiation.
  • Fast-moving local packages: mcpcap and obris show rapid version progression. If you pin pypi dependencies, plan staged upgrades and regression checks; if you float versions, expect more frequent changes.
  • Auth/env var behavior changes (compat risk): Rolli clarifies ROLLI_USER_ID is optional with a default. This reduces required config, but operators should confirm their secret/config templates won’t break validation pipelines that require non-empty values.
  • Metadata/branding updates: MarketCore, Cookiy, Valid, and SocialAPI primarily adjust website/icons/title/repo references. Low runtime risk, but can affect internal catalogs, UI display, and compliance inventories.

Why it matters for operators

  • Connectivity & policy: Hostname changes and additional transports (SSE) can break locked-down networks unless allowlists and proxy settings are updated.
  • Release management: Rapid version churn in stdio-delivered packages (pypi/npm) increases the need for pinning strategy, CI validation, and rollbacks.
  • Configuration hygiene: Small changes in env var requirements and auth header guidance can cause deploy-time failures in templated environments; validate against your config schemas.
  • Observability: When endpoints or transports change, ensure health checks, synthetic probes, and timeouts are aligned (especially for long-lived SSE connections).

Leave a Comment