Dated research · 11 October 2026 · documentary review-choice / replacement correction
A pending review is not a second-release queue
Prepare the next fix locally; do not assume a second simultaneous review of the same plugin. Decide whether the submitted package remains truthful/useful or needs deliberate wait/cancel/replacement. If a remote-MCP version is already published, keep it in place during replacement review and publish the approved replacement directly.
Use the four compact actions on Submit → Our conditional leave-valid-review default, ordering, redacted note and genuine already-working website/manual/ordinary-answer alternative are synthesis, not an official universal procedure, required form or tested fix. The alternative must serve the customer job; it is not a duplicate listing or access/review bypass.
What this inspection earns
- One active same-plugin review
- Local source preparation changes no submitted package. Submission describes waiting for the decision or cancelling the active review before replacement upload; a rejected package takes a corrected ZIP addressing feedback. Status/version handles and review email are documented, not account observations. Submission · Submit the draft.
- Resubmission wording retains its scope
- Remote-MCP guidance also describes Cancel Review and same-version-draft resubmission; new package/version updates require a complete updated-version ZIP with retained components and applicable checks/review. These descriptions do not establish one universal cancellation/upload transaction. Every resubmission starts a new review. No queue-position retention, deadline, priority, expedition or approval promise. Remote MCP review · Metadata stored during tool scanning / Submitting new versions / FAQs, Submission · Update your published plugin.
- Keep a published remote-MCP version during replacement review
- The opened canonical guidance instructs directly publishing the approved replacement without first removing the current published version. Removal without replacement causes unavailability; deletion/unpublication is not Cancel Review. This earns a narrow correction to active Maintenance captions, not a universal recipient/loaded-state guarantee. The historical 2 October report remains unchanged. Remote MCP review · Changing published metadata versions and removing the plugin / Maintenance requirements.
- Package review is not the post-publication tool path
- New hosted tools await approval; held changes retain approved definitions while calls reach live implementation. Keep the backend compatible: metadata is not preserved code. Initial package publication cannot be replaced by a scan. Held-tool Appeal/Withdraw appeal and its automatic-update pause differ from rejected-package email appeal, Cancel Review and unpublication. Support can clarify with the plugin ID, not expedite review. Submission · MCP updates / Appeal an automated finding / Submit the draft, Remote MCP review · Continuous review / Getting help / Review-time FAQ.
Primary-source basis and time limits
- Upload and submit your plugin: Submit the draft; Publish your approved plugin; Update your published plugin; Update to your MCP server; Scan your latest changes; Find and resolve tool issues; Appeal an automated finding.
- Remote MCP server review requirements: scope introduction; Metadata stored during tool scanning; Getting help / Review-time FAQ; How published MCP metadata versions work / Continuous review; Submitting new versions for review; Changing published metadata versions and removing the plugin; Maintenance requirements; update-time FAQ.
Two undated canonical primary pages independently opened and relevant body sections read. One-active-review, resubmission and direct replacement are newly inspected; draft/new-ZIP wording scope-sensitive; package/live-tool separation reconfirmed. Changed with evidence: none. Inspection is not introduction or a source/UI-change date. Saved claim summaries are not comparable full-page archives. No new equal-authority policy conflict asserted.
Unknowns and retained evidence
UNKNOWN: actual account/identity/permissions/control, selected/reviewed/published state, cancellation control/transaction, queue treatment/position, result, directory listing, intended-recipient access and loaded-session continuity. The supported replacement instruction does not cover every rejected review or enforcement removal. NOT RUN: upload, cancel, appeal/contact, provider/auth/portal, scan/deploy, installation/use/retest, guide-use and media. No lawful account/host access, consenting participant or footage supplied; no successful repair or product outcome established.
Only the review-choice/replacement claims earn 11 October. Client location 10, supporting OAuth/callback 9, creator continuity 8, CLI 7, public ZIP/conversion 6, host/dependency 5, annotation 4, commerce 3, endpoint/recorder 2, checker 1 October and unrelated 29 September retain their earned dates/conflicts. All eleven prior reports, 28 assets, original Meeting Evidence 0.1.0 source/downloads, existing tool/helper and separate 33 checker / 49 recorder histories are preserved/unrerun; ten actual-host cases remain NOT RUN. Analytics disconnected means unknown use, not zero. Runtime confirms 9 October published; retained 10 October research is a local draft, not a publication receipt. No new route/kit/widget/sample/download or broad refresh. Candidate preparation and local browser checking remain separate from Runtime acceptance/database/approval/delivery/publication.