{"version":"2.1.323","anchor":"machine-mcp-task-tickets-signed-per-tool-tickets","canonical_anchor":"machine-mcp-task-tickets-signed-per-tool-tickets","heading":"Signed per-tool tickets for remote machine MCP tools","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/machine-mcp-task-tickets-signed-per-tool-tickets","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Signed per-tool tickets for remote machine MCP tools\n\nClaude Code can now create and verify signed tickets that name one MCP tool and are tied to one session, replacing a Design login token helper\n\n**Unclear.** Whether the Design connector still gets its login token some other way.\n\n**What**\n\nMCP (Model Context Protocol) is the standard Claude Code uses to connect to outside tools. Claude Code can now create and check signed tickets for MCP tools running on a machine. Each ticket names one tool, is tied to one session, and is signed with a device key Claude Code keeps. A ticket is refused if the tool's name does not fit in it.\n\nThis takes the place of a helper that fetched a read-only login token for the Design MCP connector.\n\n**Why**\n\nIt gives remote machine MCP tools a signed ticket that proves which tool and session a request belongs to.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}