Fixed: the MCP registry published a command that is not a server
If you installed archy from the MCP registry, the handshake failed. Three defects, all on the path between archy and an MCP client (#462).
The published command could not start a server. server.json declared the package with no arguments, so a client resolved it to uvx archy: the bare console script, which has no default action. It printed usage, exited 2, and the client saw Connection closed. An external install checker had been recording archy as handshake_failed on macOS, Linux and Windows since 2026-08-15. The entry now declares the mcp subcommand, verified both by completing a real handshake and by the registry's own validator.
The listing was never actually published. The live registry entry said 0.13.3 while archy shipped 0.46.1. server.json was kept current in the repo by a test, and a checklist line said to republish it, but nothing ever did. Releases now publish the entry automatically via GitHub OIDC.
The handshake advertised the wrong version. A client asking archy what it was got the MCP SDK's version (1.28.1) on SDK 1.x, or an empty string on 2.x. It now reports archy's own version on both.
Nothing else changed
No behaviour change for anyone using archy through the CLI or an already-working MCP setup. If your client already ran archy mcp directly, you were never affected by the first two.
Full changelog: v0.46.1...v0.46.2