Daily MCP Registry Digest — 2026-03-19

by

Summary

  • Total updated servers (new latest versions observed): 13
  • Deprecated or deleted servers: None detected in provided data (no entries marked deprecated/deleted).

Notable changes

  • OpenMandate: latest is 0.5.1; remote endpoint is https://mcp.openmandate.ai/mcp (earlier versions used https://api.openmandate.ai/mcp). Operators should ensure clients are on the new host.
  • Kawa Code MCP: latest is 5.0.4 after rapid 5.0.2 → 5.0.3 → 5.0.4. Note: the 5.0.3 entry shows a package version mismatch (server version 5.0.3 but npm package version listed as 5.0.2), which can confuse automated pinning/upgrade workflows.
  • mcpcap (PCAP analysis): latest is 0.9.6 following a fast series of releases (0.6.4 → 0.7.0 → 0.8.0 → 0.9.0 → 0.9.1 → 0.9.2 → 0.9.6). Expect frequent updates and potential behavioral drift; pin versions if you need stability.
  • Pipeboard Meta Ads MCP: latest is 1.0.59 with a long run of incremental versions. If you deploy this in production, treat it like a continuously delivered service and validate changes before rolling forward.
  • PreClick / URLCheck: PreClick is present as ai.preclick/preclick-mcp@0.2.0, while ai.urlcheck/urlcheck-mcp@0.1.5 is labeled “formerly URLCheck.” This implies a migration path and possible consolidation; verify which name/endpoint your tooling uses (preclick.ai vs urlcheck.ai).
  • Marketgenius: date-stamped versioning advanced from 2026-03-15 to 2026-03-18, indicating frequent updates and likely content/tooling changes between daily builds.
  • SocialAPI: latest is 1.0.1; registry includes multiple near-simultaneous versions, suggesting churn during initial stabilization.
  • MarketCore: latest is 1.0.2 with earlier 1.0.0/1.0.1 variants; title/metadata and icon additions hint at packaging/presentation changes relevant to UI catalogs.
  • Himalayas: latest is 1.0.2sse remote was added alongside streamable HTTP.
  • Newly present (single-version, latest) servers in this snapshot: Lucid (app.lucid.mcp/lucid@0.1.0), Tabula (click.tabula.www/tabula-mcp@1.0.0), MCP Analytics (ai.mcpanalytics/analytics@1.0.4).

Why it matters for operators

  • Endpoint/host moves require coordinated cutovers: services like OpenMandate shifting from api.* to mcp.* can break clients, allowlists, and outbound firewall rules if not updated.
  • High-churn servers increase upgrade risk: rapid release trains (mcpcap, Pipeboard, Kawa Code) warrant version pinning, staged rollouts, and automated smoke tests to avoid surprise regressions.
  • Metadata inconsistencies can break automation: mismatched server vs package versions (seen in Kawa Code 5.0.3) can cause incorrect dependency resolution, cache poisoning, or failed reproducibility.
  • Naming/migration signals affect discovery and deprecation planning: the PreClick/URLCheck “formerly” note suggests consolidation; operators should standardize on one identifier and monitor for eventual delisting of legacy entries.

Updated servers (new latest versions observed)

  • ai.adadvisor/mcp-server → 1.0.1
  • ai.cookiy/cookiy → 1.7.9
  • ai.kawacode/mcp → 5.0.4
  • 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
  • co.pipeboard/meta-ads-mcp → 1.0.59
  • com.advisorfinder/mcp → 1.1.5
  • com.agentictotem/web-extractor → 1.0.5
  • church.ai.mcp/mcp-hub → 0.2.0
  • app.marketgenius/mcp → 2026-03-18

Leave a Comment