Daily MCP Registry Digest — 2026-03-11

by

Summary

  • Total updated servers (latest-version changes observed): 9
  • Deprecated servers: 0
  • Deleted servers: 0

Notable changes

  • AdAdvisor (ai.adadvisor/mcp-server) bumped to 1.0.1 with updated documentation URLs (auth remains Bearer token).
  • MarketCore (ai.marketcore/mcp) advanced to 1.0.2, adding icons and a canonical website URL; keeps both streamable-http and SSE transports.
  • Obris (ai.obris/mcp) moved to 0.4.0 across multiple interim versions; same API-key env var and both local (PyPI/stdin) and remote endpoints remain.
  • OpenMandate (ai.openmandate/mcp) jumped to 0.5.0; remote endpoint standardized on https://mcp.openmandate.ai/mcp (prior versions referenced api/openmandate hostnames).
  • Rolli (ai.rolli/mcp) updated to 1.1.6; ROLLI_USER_ID is now explicitly optional with a default, reducing required configuration.
  • Himalayas (app.himalayas/mcp) updated to 1.0.2; adds/keeps SSE in addition to streamable-http and improves server metadata (title/website/icons).
  • 402 Discovery Oracle (bot.402/discovery-oracle) updated to 1.0.1-beta with a clearer focus on discovery + trust/payment telemetry (same endpoint).
  • Compoid (com.compoid/mcp-server) progressed to 1.0.2 and added a GitHub repository link; header-based auth remains (X-Compoid-Repo-Key).
  • Pipeboard Meta Ads (co.pipeboard/meta-ads-mcp) advanced to 1.0.54 after frequent incremental releases; endpoint unchanged, but operators should expect ongoing rapid iteration.

Why it matters for operators

  • Endpoint churn and standardization: OpenMandate’s host change is the kind of update that can silently break allowlists, proxies, and egress policies if you pin domains.
  • Transport surface expansion: More servers advertising SSE alongside HTTP (e.g., Himalayas/MarketCore) means you may need distinct gateway rules, timeouts, and connection management.
  • Config simplification reduces rollout risk: Rolli making ROLLI_USER_ID optional lowers deployment friction and misconfiguration rates in templated environments.
  • Rapid-release services need tighter change control: Pipeboard’s fast version cadence suggests you should pin versions where possible (or stage upgrades) and monitor regressions/quotas closely.
  • Provenance improvements: Compoid adding a public repo link improves auditability and supply-chain review for teams with governance requirements.

Leave a Comment