Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.224,
Internal ChangesSection of the release
What
When the MCP runtime resolves to one client generation but the loaded module is from the other, a once-per-process tengu_mcp_tripwire event is emitted, carrying the expected and loaded generations (normalised to v1, v2 or other), immediately before the existing error is raised. The event name was added to the allow-listed list.
Evidence
tengu_mcp_tripwire
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
