LoginSign Up
← Back to all sparks
N

Nacos

DEVOPS
Velocity5.0

Dynamic service discovery and configuration management platform

nacos.io ↗

Nacos 3.3 makes its agent registry stable and switches authentication on by default.

service-discoveryai-registryagent-infrastructuremcpauthentication
◆Current state
Nacos 3.3.0 went final on 29 October, twelve weeks after the beta. It brings protocol-neutral agent registration and discovery, shared search across AI resources with hybrid keyword and vector retrieval, and a draft-review-publish lifecycle for MCP servers to a stable release. It also adds optional DNS service discovery and distributed locks, and enables authentication and dynamic plugin management by default. The same day, 2.5.5 shipped for the JDK 8 line with disk-path hardening and a fix for instance loss during full cluster restarts.
◆Where it's heading
Nacos is now a registry for agents, skills, prompts and MCP servers as much as for microservices, and 3.3 is the release where that becomes the supported default rather than a beta. Turning authentication on by default ends the long-standing open-by-default deployment, which will matter more than any single AI feature to operators upgrading from 3.2. The 2.x line continues as a fix-only branch.
◆Prediction
Expect 3.3.x patches dealing with migration from auth-off deployments and with the new agent and MCP APIs. 2.5.x will keep receiving backported fixes on the same days as 3.x releases.

◆Recent moves

  1. 11d ago

    3.3.0(Oct 29th, 2026)

    The stable 3.3.0 carries the beta's agent registration and discovery, vector-backed search across AI resources and a review-and-publish lifecycle for MCP servers, plus DNS discovery and distributed locks. Authentication is now on by default, the change most operators will feel on upgrade.

    View source ↗
  2. 11d ago

    2.5.5 (Oct 29th, 2026)

    The JDK 8 line gets disk-path validation, safer HTTP health checks, a fix for service instances lost during full cluster restarts and a gRPC frame corruption fix. Fixes only, released alongside 3.3.0.

    View source ↗
  3. 1mo ago

    3.3.0-RC

    The 3.3.0 release candidate added DNS service discovery and turned authentication on by default on top of the beta's agent registry. It set the shape that 3.3.0 shipped about five weeks later.

    View source ↗
  4. 2mo ago

    Deprecated AI APIs return 410; JRaft gains server-identity auth

    A security and hardening patch for the 3.2 line that carries a real breaking notice: deprecated Pipeline and legacy MCP import APIs now return 410 Gone, MCP tool imports from private or local targets require an administrator allowlist, and JRaft gRPC traffic gains server-identity authentication in a transition that cannot be rolled back once every member enforces it. This is the cleanup bill for the fast AI Registry build-out rather than new surface.

    View source ↗
  5. 2mo ago

    Two 3.2.4 fixes backported to the JDK 8 maintenance line

    Two fixes from the same day's 3.2.4 release backported to the JDK 8 maintenance branch — hardened database result resolution and health-check address validation. It confirms the 2.x line is receiving only what the 3.x line already shipped, with none of the AI Registry work.

    View source ↗
  6. 3mo ago

    Protocol-neutral agent registration and agentic resource discovery

    ⚡ SPARK

    The beta that extends the AI Registry past MCP and Skill into agents themselves, with protocol-neutral registration, endpoint discovery and legacy A2A routing. It is the origin of the arc the 3.2.x patches are now hardening around.

    View source ↗