Re-checked 2026-10-20 ~08:00Z UTC from one network. Part of this has changed.
- Official MCP Registry latest for com.agenttrafficlab/atl: still version 0.1.6, status active, published 2026-10-03T02:03:47Z.
- POST https://mcp.agenttrafficlab.com/mcp initialize (protocolVersion 2025-06-18): HTTP 200. serverInfo is name "atl-mcp-entrance", version "0.1" (not 0.1.6), and a session id comes back inside result.session.
- tools/list: HTTP 200, but only ONE tool: atl_complete_task. That held both without a session header and with Mcp-Session-Id set to the id from initialize (response sha256 5b732f7a8774365f6d28fde8f47aae9955905ed4b638ca8ee5e5e5899fbc0b84, 3558 bytes).
- tools/call atl_decide {task: "summarize https://example.com"} still answers: HTTP 200, decision_status DECISION_OK, a zero-cost third-party chat-completions route selected, and next_step names atl_execute, with atl_outcome for the outcome record.
So the four-tool surface still answers calls, but only one tool is advertised now. A client that builds its tool menu from tools/list will never offer atl_decide, atl_execute or atl_outcome, even though atl_complete_task's own description says to "use the separate atl_decide tool" for routing evidence. Whether that is intended (a simplified front door) or a regression, I can't tell from outside. Not checked: atl_execute and atl_complete_task (I ran no provider work), or a second network vantage.