MCP Events
A draft extension to the MCP protocol that introduces the capability for servers to proactively push events to clients. It expands the interaction model from unidirectional request-response to bidirectional subscription-based push, supporting use cases such as monitoring alerts, data updates, and task-completion callbacks.
Timeline (last 90 days)
When using MCP Events, you should first get signature verification and the task template working in a clear single-point scenario, then gradually expand the trigger sources and monitor the 30-per-hour quota to prevent exhaustion.
MCP Events officially allows at most 30 task runs to be triggered per hour.
MCP Events requires signature verification of callback requests: developers compute a signature over the raw request body using a secret key and compare it with the signature in the request header, and must reject the request outright if verification fails.
Signature computation must be based on the raw request body rather than content re-serialized after parsing, otherwise byte-level differences will cause verification to fail; the secret key should be injected via environment variables rather than hard-coded.
Because MCP Events allows only 30 triggers per hour, its positioning is a low-frequency, high-value automation node rather than a high-throughput batch processing pipeline.
For high-frequency event scenarios, trigger counts should be reduced through aggregation design or pre-filtering, reserving the 30-trigger quota for events that truly require model judgment.
Vercel Connect has officially entered the public beta of MCP Events, allowing developers to let applications and Agents subscribe to webhook events from MCP-compatible servers.
ChatGPT is adding draft support for MCP Events, allowing MCP servers to proactively push events to clients.
The core argument put forward in the article is that a subscription is essentially a credential, because it grants an external system ongoing permission to proactively reach a user's session in the future.
A subscription, as a continuously valid authorization, should be managed as a credential, requiring a clear holder, scope, lifecycle, and a mechanism by which it can be revoked.
2 more timeline events
All Facts (10)
When using MCP Events, you should first get signature verification and the task template working in a clear single-point scenario, then gradually expand the trigger sources and monitor the 30-per-hour quota to prevent exhaustion.
50%UnverifiedMCP Events requires signature verification of callback requests: developers compute a signature over the raw request body using a secret key and compare it with the signature in the request header, and must reject the request outright if verification fails.
50%UnverifiedSignature computation must be based on the raw request body rather than content re-serialized after parsing, otherwise byte-level differences will cause verification to fail; the secret key should be injected via environment variables rather than hard-coded.
50%UnverifiedBecause MCP Events allows only 30 triggers per hour, its positioning is a low-frequency, high-value automation node rather than a high-throughput batch processing pipeline.
50%UnverifiedFor high-frequency event scenarios, trigger counts should be reduced through aggregation design or pre-filtering, reserving the 30-trigger quota for events that truly require model judgment.
50%UnverifiedMCP Events officially allows at most 30 task runs to be triggered per hour.
50%UnverifiedThe core argument put forward in the article is that a subscription is essentially a credential, because it grants an external system ongoing permission to proactively reach a user's session in the future.
50%UnverifiedA subscription, as a continuously valid authorization, should be managed as a credential, requiring a clear holder, scope, lifecycle, and a mechanism by which it can be revoked.
50%UnverifiedA common industry solution for credential revocation is 'short window + strong validation': setting extremely short token expiration times while querying an authoritative state source in real time before each push to verify subscription validity.
50%UnverifiedChatGPT is adding draft support for MCP Events, allowing MCP servers to proactively push events to clients.
50%