Check whether a modern MCP client or server correctly advertises the Tasks extension before task-based execution is used.
Tasks are no longer an experimental core feature. In MCP 2026-07-28 they live in the io.modelcontextprotocol/tasks extension and are explicitly advertised through the extensions framework.
Validate MCP Tasks extension advertisements and detect missing io.modelcontextprotocol/tasks capability declarations.
Use MCP Tasks Extension Validator as a focused pre-flight utility while building, reviewing or debugging an MCP integration. Paste the relevant configuration, protocol message, metadata, schema or value into the tool and review the returned findings before the same data reaches a production client or server.
Extensions add optional behavior outside the MCP core. Both sides should explicitly support the extension being used, and extension-specific data should be validated separately from the base protocol envelope.
A clean result means the input passed the rules implemented by this utility. It does not guarantee application security, protocol interoperability or correct business behavior. Test important integrations against the exact MCP client, SDK, gateway and server versions used in your deployment.