Changed
- The oam floor moves from 0.19.5 to 0.20.2, so the
tailscale-mcplauncher no longer runs the server on oam 0.19.5-0.20.1. 0.20.2 is verified on the installed binary (oam 0.20.2) through the launcher withOAM_BINpointing at it andTAILSCALE_MCP_RUNTIME=oam: a full MCP handshake listing all 98 tools and all 4 resources,tailscale_tool_groupsanswering, a call with invalid arguments returning the same error, and the whole session byte-identical to the same session on Node, with no non-JSON line on stdout. The same session answers fromoam run bin/tailscale-mcp.mjs(in-process), fromoam run src/index.ts(no build step), and withTAILSCALE_MCP_SANDBOX=1. An oam below 0.20.2 is handled as any below-floor oam: Node underauto, an error underTAILSCALE_MCP_RUNTIME=oam. Runoam self-update.
Security
hono4.13.18 (was 4.13.13; override floor raised to^4.13.16), clearing Dependabot alerts #56-#60:csrf()skippingtext/pingrequests,mount()paths bypassing prefix-scoped middleware, RegExpRouter skipping wildcard middleware,validator('form')skipping multipart validation, andcsshelper HTML injection.honoreaches this package only through@modelcontextprotocol/sdk.npm auditreports 0 vulnerabilities.