Daily MCP Registry Digest — 2026-02-28

Summary

  • Total updated servers (new release published): 10
  • Deprecated servers: 0
  • Deleted servers: 0

Updated servers (latest versions)

  • com.civic/nexus: 0.1.104 → 0.1.105
  • com.linkbreakers/mcp: 1.25.1 → 1.25.7 (multiple rapid releases)
  • com.smartbear/smartbear-mcp: 0.14.0 → 0.14.1
  • com.teamwork/mcp: 1.10.2 → 1.10.3
  • io.github.0ics-srls/ui-ticket-mcp: 1.1.3 → 1.1.5
  • io.github.Aryan-Jhaveri/mcp-statcan: 0.1.4 → 0.2.1
  • io.github.Codeturion/codesurface: 0.4.1 → 0.6.0
  • io.github.Codeturion/unity-api-mcp: 2.0.1 → 2.0.2
  • io.github.Fabric-Protocol/fabric: 0.1.0 → 0.2.0 (auth/bootstrap flow changed; description updated)
  • io.github.atef-ataya/depwire: 0.2.5 → 0.3.1 (tool count/docs-oriented features indicated in description)

Notable changes

  • High-churn release train: Linkbreakers pushed six sequential patch versions (1.25.1 → 1.25.7). Expect frequent updates and potential behavior drift if you auto-track latest.
  • Auth/bootstrap behavior updated: Fabric Marketplace now indicates a bootstrap tool path with “no auth needed” and changes the Authorization header guidance (ApiKey format adjusted). This can break existing automation if credentials/headers are assumed.
  • Operator platform components moved: Civic Nexus gateway and SmartBear/Teamwork integrations each cut new point releases—likely bugfix/compatibility updates that matter if these are in your critical path.
  • Developer productivity/indexers iterating fast: codesurface jumped 0.4.1 → 0.6.0 and depwire advanced through multiple versions, signaling ongoing API/tool-surface evolution.

Why it matters for operators

  • Pinning and controlled rollout: Rapid multi-release sequences (notably Linkbreakers; also depwire/codesurface) increase the risk of unnoticed breaking changes. Prefer version pinning with staged promotion and an explicit update cadence.
  • Credential and request-shape validation: Any change in stated auth/header formats (Fabric) can translate into runtime failures (401/403) and incident noise. Re-validate client configuration and secret templates when upgrading.
  • Gateway/integration reliability: Updates to gateway and automation servers (Civic Nexus, Teamwork, SmartBear, Postman-style integrations) directly impact agent-to-tool connectivity. Track these in your dependency SBOM and monitor error budgets post-upgrade.

Leave a Comment