MCP server publishes failing scores on a public lost-response retry contract
A developer team scored its own MCP server against a public test contract for handling lost responses after mutating tool calls. The contract addresses MCP issue #3394, which reports that retrying a mutating call can re-execute external effects. The scoring was published before the run, and each assertion is graded separately as pass, fail, or unproven, with no aggregate score. The team's own baselines show failures, including a production run that produced two effects for one logical operation and a mismatched-parameter retry that executed as a normal new call. The contract is a draft under joint review with an external collaborator and is designed for independent reproduction by anyone.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in