Skip to content- Sources: docs, HN discussion
- Summary: OpenAI's documentation describes MCP Events as a mechanism where an MCP server delivers updates to a subscribed ChatGPT conversation over a webhook, rather than ChatGPT calling the server. The documentation carries the matching controls as requirements rather than advice: verify the callback with a single-use signed challenge, require HTTPS, block private and non-public addresses, refuse redirects, sign every delivery with Standard Webhooks, and treat user-authored text in a payload as data rather than instructions.
- Why it matters: A server can now wake ChatGPT, so an inbound comment or chat message turns into an agent run with no person present.
- Follow-up: Track whether the documented controls are enforced by the platform or left to each server operator.