Daily MCP Registry Digest (2026-03-18)

by

Daily MCP Registry Digest (2026-03-18)

Summary

  • Total updated servers (new latest versions observed): 19 (servers with multiple versions in the snapshot and a newer isLatest:true entry).
  • Deprecated servers: None observed (no status set to deprecated).
  • Deleted servers: None observed (no entries indicating removal; snapshot only shows active).

Notable changes

  • Cookiy advanced through multiple releases to 1.7.9 (several intermediate versions present). Repository reference also differs between older and newer entries (code repo vs skill repo), which can affect source-of-truth and SBOM/auditing workflows.
  • mcpcap shows rapid iteration from 0.6.4 → 0.9.6 (Python stdio package). High churn suggests breaking/behavioral changes are more likely; pinning and staged rollouts recommended.
  • OpenMandate moved to 0.5.1 after several prior versions; endpoint is standardized to https://mcp.openmandate.ai/mcp in newer releases (older entries include https://api.openmandate.ai/mcp).
  • MarketCore updated to 1.0.2 and added more complete metadata (title/website/icons) while keeping both streamable-http and sse transports.
  • Rolli updated to 1.1.7 and changed ROLLI_USER_ID from required to optional (defaulting to "rolli-mcp"). This reduces configuration burden but can change tenant routing assumptions.
  • Himalayas updated to 1.0.2 and expanded capability to include sse transport alongside streamable-http, plus title/icon metadata updates.
  • SocialAPI updated to 1.0.1 after confusing/overlapping version declarations in earlier entries (server version vs npm package version). Operators should treat the npm mcp-socialapi@1.0.1 as the deployable artifact.
  • Valid “Chat With Your Ads” updated to 1.0.1 with minor metadata normalization (icons field shape); endpoint unchanged.
  • AdvisorFinder updated to 1.1.5; repository pointer changed earlier in the chain (from sec-advisor-project to advisorfinder-mcp), relevant for provenance tracking.
  • AgenticTotem Web Extractor updated to 1.0.5 with icon ordering/packaging metadata adjustments; endpoint unchanged.
  • Apify MCP Server updated to 0.9.11 after multiple prior versions; remote remains https://mcp.apify.com/ with required Bearer auth header.
  • Pipeboard Meta Ads MCP advanced to 1.0.59 (many increments). High release frequency indicates operators should pin versions and monitor changelogs closely.
  • URLCheck → PreClick naming transition appears as separate server identities (ai.urlcheck/urlcheck-mcp and ai.preclick/preclick-mcp). Newly deployed clients should standardize on PreClick endpoints (preclick.ai), but legacy URLCheck endpoint (urlcheck.ai) still appears active in this snapshot.

Why it matters for operators

  • Endpoint drift and transport changes: Several servers add or standardize transports (notably SSE alongside HTTP) and/or change base URLs (e.g., OpenMandate). This affects allowlists, proxies, and egress controls.
  • High-churn packages: Projects with many rapid releases (mcpcap, Pipeboard, Cookiy) increase upgrade risk. Use version pinning, canary rollouts, and regression tests around tool schemas and response formats.
  • Auth and secret handling: Many servers require Bearer tokens or API keys via headers/env vars. Ensure secret managers and runtime policies (no-log for headers, redaction) are consistent, especially when switching between remote vs stdio deployments.
  • Provenance/compliance: Repository references changing across versions can break internal supply-chain assertions. If you rely on repo URLs for auditing, re-validate provenance when a server’s repo field changes.
  • Naming/identity continuity: The URLCheck/PreClick split shows how renames can appear as new server names instead of a formal deprecation. Operators should map aliases to avoid duplicated integrations and inconsistent policy enforcement.

Servers with new latest versions in this snapshot (19)

  • ai.adadvisor/mcp-server → 1.0.1
  • ai.cookiy/cookiy → 1.7.9
  • ai.marketcore/mcp → 1.0.2
  • ai.mcpcap/mcpcap → 0.9.6
  • ai.obris/mcp → 0.4.0
  • ai.openmandate/mcp → 0.5.1
  • ai.rolli/mcp → 1.1.7
  • ai.social-api/socialapi → 1.0.1
  • app.himalayas/mcp → 1.0.2
  • bot.402/discovery-oracle → 1.0.1-beta
  • church.ai.mcp/mcp-hub → 0.2.0
  • co.pipeboard/meta-ads-mcp → 1.0.59
  • co.valid/chat-with-your-ads → 1.0.1
  • com.advisorfinder/mcp → 1.1.5
  • com.agentictotem/web-extractor → 1.0.5
  • com.apify/apify-mcp-server → 0.9.11

Note: Counts are derived from servers that include multiple versions in the provided snapshot and have a newest entry marked isLatest:true. Single-version servers may still be “recently published” but are not counted as “updated” without an older version present in this dataset.

Leave a Comment