Under the hood
Useful2 Signal2
An MCP client version mismatch now reports the two versions before raising its error.
What's wrong with this entry?
Anonymous. No account, no email.
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.