Skip to content
Overview
- Total updated servers (new “isLatest” versions observed): 8
- Deprecated servers: 0
- Deleted servers: 0
Updated servers (latest version bumps)
- AdAdvisor MCP Server (ai.adadvisor/mcp-server): 1.0.0 → 1.0.1 (website/docs URL and auth header guidance updated; endpoint unchanged: https://api.adadvisor.ai/mcp)
- Pipeboard Meta Ads MCP (co.pipeboard/meta-ads-mcp): 1.0.46 → 1.0.47
- Civic Nexus (com.civic/nexus): 0.1.104 → 0.1.105
- Linkbreakers MCP (com.linkbreakers/mcp): 1.25.1 → 1.26.0 (multiple rapid interim releases)
- Singapore Business Directory (com.sgpdirectory/mcp): 1.0.2 → 1.3.0 (adds title/icons/website, and explicit Authorization header templating for remote usage)
- SmartBear MCP (com.smartbear/smartbear-mcp): 0.14.0 → 0.14.1
- Proxy Doctor (io.github.Jiansen/proxy-doctor): 0.1.1 → 0.2.1 (three releases same day)
- Statistics Canada MCP Server (io.github.Aryan-Jhaveri/mcp-statcan): 0.1.4 → 0.3.0 (multiple interim versions)
Notable changes
- High-churn release trains: Linkbreakers (1.25.1→1.26.0) and Proxy Doctor (0.1.1→0.2.1) indicate active development—expect potential tool/behavior changes even when descriptions stay similar.
- Registry metadata/auth formatting updates: Singapore Business Directory 1.3.0 now includes a concrete
Authorization: Bearer {SGP_DIRECTORY_API_KEY} pattern for the remote, which can affect how clients template secrets.
- Docs/website pointers moved: AdAdvisor 1.0.1 updated documentation URLs in metadata; operators relying on automated doc links should refresh references.
- Multi-version histories present: Several entries show many non-latest versions retained in the feed (e.g., Judges Panel, Fabric Marketplace, codesurface). This isn’t a deprecation signal, but it does raise the odds of clients pinning to stale versions if selection logic is wrong.
Why it matters for operators
- Pin and verify: For fast-moving servers, pin exact versions in your deployment manifests and advance only after smoke tests (tool list, auth, and transport behavior).
- Secret injection compatibility: Changes in how remotes specify headers/variables (e.g., explicit Bearer templating) can break templating or lead to double-Bearer prefixes—validate client config generation.
- Supply-chain posture: Where multiple packaging types exist (npm/pypi/nuget/oci/mcpb), ensure your org’s allowed artifact sources and signature/hash verification policies are applied consistently.
- Operational hygiene: High update frequency is a cue to review rate limits, error budgets, and rollback procedures for integrations that are on the critical path (ads, compliance, CI/CD, gateways).
