Skip to content
Summary
- Total updated servers (new latest versions): 11
- Deprecated servers: none observed in provided data
- Deleted servers: none observed in provided data
Updated servers (new latest)
- ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (docs/website URL and auth header guidance updated; remote endpoint unchanged)
- ai.marketcore/mcp: 1.0.0 → 1.0.2 (title/website added, icons added; transports remain streamable-http + SSE)
- ai.obris/mcp: 0.2.5 → 0.2.6 (PyPI package version bump; API key env var unchanged)
- ai.rolli/mcp: 1.1.4 → 1.1.6 (env var semantics adjusted: ROLLI_USER_ID now optional with default)
- app.himalayas/mcp: 1.0.0 → 1.0.2 (adds SSE remote; description expands to include posting jobs)
- co.pipeboard/meta-ads-mcp: 1.0.46 → 1.0.50 (incremental releases; remote unchanged)
- com.apify/apify-mcp-server: 0.9.3 → 0.9.7 (incremental releases; remote unchanged)
- com.civic/nexus: 0.1.104 → 0.1.108 (rapid patch cadence; remote unchanged)
- com.fourmemeclaw/kuro-mcp: 1.0.0 → 1.1.0 (description clarified, icons added; remote unchanged)
- com.microsoft/azure: 2.0.0-beta.23 → 2.0.0-beta.24 (new beta build across NuGet/NPM/PyPI plus refreshed MCPB artifacts and hashes)
- com.senzing/mcp: 0.13.1 → 0.15.0 (high-frequency releases; latest is 0.15.0)
Notable changes
- Transport surface expansion: Himalayas adds an SSE endpoint alongside streamable-http, which may change client connection behavior and firewall/egress considerations.
- Operational metadata improvements: MarketCore and Kuro add icons/website/title refinements; AdAdvisor updates documentation links and auth guidance. These are low-risk changes but can affect cataloging and internal tooling that relies on metadata.
- Artifact refresh & supply-chain implications: Microsoft Azure MCP Server beta.24 includes new downloadable MCPB artifacts and new SHA-256 hashes—operators should update allowlists and verify integrity in build pipelines.
- Config contract change (minor): Rolli makes
ROLLI_USER_ID optional with a default, potentially reducing required configuration for deployments.
- High-churn vendors: Senzing, Apify, Civic Nexus, and Pipeboard show rapid release cadence within a short window.
Why it matters for operators
- Upgrade planning: Fast-moving servers increase drift risk; pin versions where stability matters and schedule controlled rollouts for high-churn dependencies.
- Connectivity & runtime policy: New/added SSE endpoints (e.g., Himalayas) can require different proxy timeouts, connection limits, and observability dashboards compared to request/response HTTP.
- Security posture: New binary artifacts/hashes (Azure MCP) require renewed provenance checks; treat hash changes as a trigger to re-validate your supply-chain verification and artifact mirror rules.
- Configuration management: Small env-var contract changes (Rolli) can break strict validators or Helm charts; update schemas and CI checks to match the latest requirements.
