The report
Two advisories in the MCP Python SDK require different deployment checks, even though both involve who may use an agent service.
First identify the code path
The experimental-task advisory applies when an application enables the affected task handlers. It concerns one connected client reading or cancelling another client’s work. Version 1.27.2 introduces automatic binding for SDK-generated task IDs, while custom IDs and custom handlers still require ownership review.
The WebSocket advisory concerns a deprecated helper manually wired into an ASGI application. The maintainer excludes FastMCP, stdio, SSE and Streamable HTTP from that advisory. Version 1.28.1 adds Host/Origin validation support, but omitting the new settings leaves it disabled.
Why the distinction matters
A package inventory establishes which dependency is installed, not which transport or handler the application exposes. Review the initialization code and the actual authorization policy. For tasks, test access between different principals; for the WebSocket helper, verify that untrusted origins and hosts are rejected and that authenticated clients remain limited to permitted actions.
What this update does not establish
The cited advisories do not establish exploitation in the wild or a victim count. A published patch is not proof that every affected deployment has applied and configured it. The linked Cases preserve affected versions, source locators and the limits of the remediation evidence.