Daily MCP Registry Digest — 2026-03-16

Daily MCP Registry Digest (2026-03-16)

Overview

  • Total updated servers: 10
  • Deprecated servers: 0 observed
  • Deleted servers: 0 observed

Updated servers (new latest versions)

  • ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (docs URL updated; auth header guidance links changed).
  • ai.marketcore/mcp: 1.0.0/1.0.1 → 1.0.2 (adds websiteUrl; naming/metadata normalization; icon present on later versions).
  • ai.obris/mcp: 0.2.5 → 0.2.6 → 0.3.0 → 0.4.0 (continued evolution; stdio package + hosted remote retained).
  • ai.openmandate/mcp: 0.3.1 → 0.3.2 → 0.3.3 → 0.5.0 → 0.5.1 (remote URL moved from api.openmandate.ai to mcp.openmandate.ai).
  • ai.rolli/mcp: 1.1.4 → 1.1.5 → 1.1.6 → 1.1.7 (ROLLI_USER_ID becomes optional with default behavior).
  • ai.social-api/socialapi: 0.1.0 / 1.0.0 → 1.0.1 (metadata alignment; current latest is 1.0.1).
  • app.himalayas/mcp: 1.0.0 → 1.0.1 → 1.0.2 (capabilities expanded: search + post; adds SSE transport and richer metadata).
  • bot.402/discovery-oracle: 1.0.0-beta → 1.0.1-beta (description emphasizes ranked endpoints, trust, payment telemetry/x402 surfaces).
  • co.pipeboard/meta-ads-mcp: 1.0.46 → … → 1.0.57 (rapid release cadence; same remote endpoint across versions).
  • com.apify/apify-mcp-server: 0.9.10 → 0.9.11 (incremental update; endpoint/auth model unchanged).

Newly published (recent additions in this snapshot)

  • ai.filtrix.mcp/filtrix-ai 0.1.0 (image/video generation; requires Authorization bearer token).
  • ai.scamverify/mcp 1.0.0 (threat verification for phone/URL/text/email).
  • com.agentictotem/web-extractor 1.0.5 (web extraction with JSON Schema; pay-per-use via x402).

Deprecated or deleted

  • No entries in this dataset are marked deprecated, and no deletions are indicated.

Notable operator-impacting changes

  • Endpoint migration: OpenMandate remote moved to https://mcp.openmandate.ai/mcp from https://api.openmandate.ai/mcp. Operators should update allowlists, egress rules, and health checks.
  • Transport surface area increase: Himalayas and MarketCore advertise SSE in addition to streamable-http, expanding routing/proxy considerations and connection management.
  • Config simplification: Rolli makes ROLLI_USER_ID optional (default provided), reducing required secrets/config for deployments.
  • High churn package: Pipeboard Meta Ads continues frequent version bumps; pin versions and plan controlled rollouts if you rely on its tool behavior.

Why it matters for operators

  • Reduced outage risk: catching endpoint moves early prevents 404/connection failures when vendors shift traffic.
  • Security posture: many servers require bearer tokens in headers; ensure secrets handling, scoped tokens, and egress controls are consistent with new/changed docs.
  • Runtime compatibility: mixed transports (stdio, streamable-http, SSE) affect how you deploy gateways, manage long-lived connections, and observe latency/error budgets.
  • Change management: fast-moving integrations (e.g., Ads tooling) benefit from version pinning, canary deploys, and automated contract tests for tools.

Leave a Comment