Daily MCP Registry Digest — 2026-02-27

by

Overview

  • Total updated servers (new latest version): 10
  • Deprecated servers: 0
  • Deleted servers: 0

Updated servers (latest version changes)

  • com.civic/nexus: 0.1.104 → 0.1.105
  • com.linkbreakers/mcp: 1.25.1 → 1.25.7 (multiple rapid releases)
  • com.microsoft/esrp-oss-mcp-test: 26.226.135743 → 26.227.55504 (also updates across npm/pypi/nuget/OCI/mcpb artifacts)
  • 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.Fabric-Protocol/fabric: 0.1.0 → 0.2.0 (notable auth guidance change: bootstrap tool called out as no-auth path)
  • io.github.IBazylchuk/paparats-mcp: 0.2.12 → 0.2.14
  • io.github.KevinRabun/judges: 2.2.0 → 2.3.0 (judge count in description increases 33 → 34)
  • io.github.Mediaeater/swarm-at: 0.6.1 → 0.7.1 (description indicates blueprint expansion 32 → 48 over the sequence)
  • io.github.Pattyboi101/indiestack: 0.3.0 → 0.4.0 (catalog count in description increases 356+ → 358+)
  • io.github.ShirBarZur/planform-mcp: 1.0.6 → 1.0.7
  • io.github.airweave-ai/search: 0.9.0 → 0.9.1
  • io.github.atef-ataya/depwire: 0.2.5 → 0.3.1 (tool count in description increases 10 → 12 across the sequence)

Note: Registry listings include multiple historical versions for some servers; the items above reflect those that currently show an older entry plus a newer isLatest:true entry in the provided data.

Notable changes

  • Rapid patch trains: Linkbreakers shipped 6 incremental versions (1.25.1→1.25.7) in a short window, suggesting active fixes or operational tuning.
  • Multi-artifact maturity: Microsoft ESRP OSS test server updated with coordinated package updates across ecosystems (npm, PyPI, NuGet, OCI, MCPB), which can affect supply-chain pinning and installation paths.
  • Capability growth signaled via descriptions: Depwire (more tools), Judges Panel (more judges), Swarm-at (more blueprints), IndieStack (larger catalog). Even if APIs are stable, operators should expect behavior and output surface area to expand.
  • Auth/onboarding ergonomics: Fabric v0.2.0 adjusts how API key acquisition is communicated (bootstrap tool highlighted as starting point), which changes how operators document and secure initial provisioning.

Why it matters for operators

  • Version pinning & rollout control: Frequent releases (e.g., Linkbreakers) increase the need for explicit version pinning, staged rollouts, and quick rollback paths.
  • Credential and policy review: Updates that touch auth flows or environment variables (notably API-key based remotes) should trigger a review of secret distribution, rotation, and least-privilege policies.
  • Supply-chain hygiene: Servers shipping via multiple registries/artifacts (npm/pypi/nuget/OCI/MCPB) require consistent provenance checks, digest pinning (for OCI), and checksum validation (for MCPB) in CI/CD.
  • Client compatibility: Expanding tool surfaces can impact client caps, rate limits, and permissions—ensure allowlists/denylists and tool-discovery caches are refreshed after upgrades.

Leave a Comment