Skip to content
Summary
- Total updated servers (latest version advanced): 10
- Deprecated servers: 0
- Deleted servers: 0 (no deletions indicated in the provided data)
Updated servers (high-signal changes)
- ai.adadvisor/mcp-server: 1.0.0 → 1.0.1 (website/docs URL updated; auth header guidance updated).
- co.pipeboard/meta-ads-mcp: 1.0.46 → 1.0.47 (patch update).
- com.boostedchat/travel: 0.1.1 → 0.1.2 (adds/advertises PyPI package alongside npm; packaging surface expanded).
- com.civic/nexus: 0.1.104 → 0.1.105 (patch update).
- com.linkbreakers/mcp: 1.25.1 → … → 1.26.3 (rapid multi-release bump; latest is 1.26.3).
- com.sgpdirectory/mcp: 1.0.2 → … → 1.3.2 (auth header formalized as Bearer token variable; website URL changes; multiple intermediate releases).
- com.smartbear/smartbear-mcp: 0.14.0 → 0.14.1 (patch update; env var contract appears stable).
- com.teamwork/mcp: 1.10.2 → 1.10.3 (OCI image tag bumped; runtime env vars unchanged).
- com.versedb/versedb-mcp: 1.0.0 → 1.0.1 (patch update).
- io.github.Aryan-Jhaveri/mcp-statcan: 0.1.4 → … → 0.4.1 (fast-moving minor releases; latest is 0.4.1).
Notable changes & patterns
- High churn / rapid release trains: Linkbreakers (1.25.x → 1.26.3), SGPDirectory (1.0.x → 1.3.2), StatCan (0.1.x → 0.4.1). Expect frequent pin/upgrade decisions and increased CI noise if tracking latest.
- Packaging surface expansion: BoostedTravel now includes both npm and PyPI distributions in the registry entry, increasing installation options but also creating more places for version skew.
- Auth/documentation normalization: SGPDirectory and AdAdvisor entries emphasize Bearer-token style headers and variable-based injection; this improves operator automation but can break if your tooling assumed older header formats or endpoints.
Why it matters for operators
- Pinning vs. tracking latest: Rapidly iterating servers can introduce behavioral changes or subtle contract drift between days even when changes look “patch-level.” Consider pinning versions in production and promoting via staging.
- Install/packaging choices affect fleet consistency: When a server is available via multiple ecosystems (npm/PyPI/OCI/mcpb), standardize on one distribution path to reduce drift and simplify SBOM and vulnerability management.
- Auth header expectations: Several entries rely on Authorization/Bearer patterns and secret variables; validate that your secret injection and redaction policies (logs, tracing, prompt captures) correctly treat these as secrets.
- Release monitoring: For high-churn services, set alerting on latest changes and maintain an allowlist of approved versions to avoid surprise upgrades by automated installers.
