The page says developers upload a ZIP and can inspect automated findings before submitting for review. It also separates package checks from hosted server scans: Metadata & Skills shows the uploaded package version, while MCPs shows the connected server and its scanned tools.
The mechanism is that different change surfaces receive different handling. Package metadata and skills are corrected in the source package and submitted again as a ZIP, while hosted MCP server changes can be checked directly. The documentation states: After initial publication, changes to your MCP server are picked up automatically, and eligible updates go live once they pass automated checks. This should reduce the need to resubmit the entire package for qualifying server-side changes, though eligibility is not defined in the supplied excerpt.
The public page also says only one MCP server can be connected per plugin. The supplied evidence is documentation, not a measured account of operational performance or a dated announcement; these details describe the documented process, not proof of adoption or outcomes. Watch whether OpenAI clarifies which updates are eligible for automatic publication and how developers are informed when checks fail.