Published plugin: Rescan disabled, stale MCP metadata blocks UI release

hey! We maintain Wander’s public directory plugin, and its MCP metadata is stuck on the November 12 scan. Both Rescan and Reconnect are disabled with “Scan unavailable.” This is blocking release of our interactive listings UI, a critical feature for us.

The plugin package and live server are now v0.8.0, but the published connection still uses the older tool definition. We compared them directly:

  • The live search_listings descriptor includes _meta.ui.resourceUri and openai/outputTemplate. Reading the linked resource returns the HTML successfully.
  • The portal’s downloaded published definition has templates: null, no UI linkage, and the old tool description.
  • A direct local MCP connection to the same endpoint loads the UI frame in Codex. The public connector returns listing data without starting that frame.

Scanning remains disabled despite no active scan or appeal. The domain is verified, the server uses no authentication, and the portal reports no findings. This is a public plugin managed through the developer portal, so workspace app refresh and OAuth token guidance don’t apply.

We found similar reports from Terraform Academy and wp2ai and Sekai. We don’t know whether the underlying cause is the same.

Plugin: plugin_asdk_app_6af5c69d8d3481918791b49cab9f8fe4
MCP endpoint: https://mcp.wander.com/mcp/chatgpt

Has anyone recovered this state while keeping the same public plugin identity? Could @OpenAI_Support route this to the team that can repair the scan connection and restore Rescan? We’ve already shared diagnostics privately with Support, but don’t yet have confirmation that the responsible engineering team has accepted the investigation.

Small update: we planned to test unpublishing and then republishing the existing plugin, but the portal blocks that too. The “Unpublish plugin?” dialog says:

This plugin’s releases are managed separately from its app. Contact support to unpublish it.

The Unpublish plugin button is disabled, so nothing was unpublished or deleted and we could not run the republishing test. We don’t know whether this restriction and the disabled scan controls share a cause. We’ve added this finding to our existing Support thread; the interactive listings UI release remains blocked.