Dated research · 12 October 2026 · publication versus placement
Missing directory placement is not a publication diagnosis
A missing main-page tile is not the publication test. Establish actual chosen Publish, then check the exact publication name or directory URL from the submission portal. No actual successful check is supplied here: do not infer “merely unfeatured” or dismiss a real access failure.
Use the four compact actions on Business → Our default, ordering, redacted note, stop rule and genuine ordinary-service alternative are synthesis / untested, not official mandates, demonstrated remedies, universal availability or an acquisition verdict.
The next decision, not another placement recipe
- Establish publication. Approval precedes the distinct chosen Publish action. Confirm the intended identity/version/state and publication name in the actual authorized context.
- Use the documented handles. Exact publication-name search or the portal-supplied directory URL is more specific than main-page browsing or a guessed link. Enhanced main-page distribution is discretionary and not requestable. Documented checks are not observed successful results.
- Keep a genuine failure actionable. Retain actual state/name/URL provenance/surface/recipient/redacted error/time and legitimate plugin-ID identification. Seek owning clarification if unresolved; pause claims that the recipient can use it. A maintainer’s listing reach proves neither permitted installation nor provider access, selection or useful output.
- Choose the useful customer task. Unpublish/resubmit/rename/repackage is not an established enhanced-placement remedy. Correct independently evidenced defects. Truthful intent-scoped tool descriptions must not game model selection. A genuine existing website/service or ordinary workflow is an optional sufficient alternative, not a tested drop-in or review/access bypass.
Remote MCP review · Publish / Discovery / publication FAQs; Guidelines · Overview / Purpose / Fair play / tool descriptions. No traffic, conversion, customer value, revenue or recommendation guarantee established.
Primary source comparison and narrow evidence delta
- V01–V03 · PUBLICATION HANDLES
- Remote MCP server review requirements → Publication and distribution → Publish the plugin / Discovery / Publication and Distribution FAQs, first approval/automatic-listing question and second missing-directory question. Approval/Publish and selected enhanced placement reconfirmed; exact publication-name or portal-directory-URL precision newly inspected relative to the guide’s earlier generic caption, not a newly introduced feature. Missing tile alone cannot diagnose failed publication.
- V04–V06 · SCOPE AND METADATA
- Plugin guidelines → Overview / Plugin fundamentals → Purpose and originality / Safety → Fair play / MCP requirements → Tools → Descriptions that match behavior. Utility and truthful behavior are requirements, not a placement ranking recipe. Remote-MCP public flow is not every local/workspace channel, host or recipient. No new consequential conflict established; no source precedence over older conflicts inferred.
- V07–V08 · ACTUALS AND SYNTHESIS
- No account, Publish event, exact route or recipient is supplied. Default/order/note/stop and investment fork synthesize scoped documentation; untested, not required official procedure. Real failure needs lawful evidence and clarification, not a harmless-unfeatured diagnosis.
- REUSED, NOT RE-FETCHED
- 11 October help evidence supplies plugin-ID identification for legitimate clarification, not placement or expedition. 8 October recipient evidence separates creator access from intended teammate reach/install/select/output in Enterprise/web/Chat scope; exact UI sequence does not transfer to all remote-MCP hosts. Saved 6 October Audience E03 motivates a distribution hypothesis only, not a real observed visibility failure or acquisition outcome.
Method and unobserved actuals
Runner independently opened only the two commissioned canonical pages after official-domain searches and targeted section reads within 12 October 17:59:58–18:00:46 UTC. Undated pages; clocks bracket research calls, not per-request HTTP, change, launch or rollout dates. Search excerpts and saved summaries cannot date a change. Changed with evidence: none. Publisher reviewed that saved ledger at 18:07:56 UTC; answer checked_at and new V accessed_at record that review, not a new fetch. Incidental neighboring extraction does not refresh review, auth or commerce.
Actual identity/permissions/control, selected Publish/version/name/URL, search/link behavior, account/surface/recipient availability, installation, provider access, selection, loaded capability, output and value: UNKNOWN. Publication/search/link/contact/install/use, provider/portal/workspace/login, scan/deploy/retest, guide/participant, analytics and media operations: NOT RUN. No probe, screenshot, supplied failure reproduction, support contact or participant observation. Analytics is disconnected, not zero use; no traffic/demand claim.
Retained evidence and release status
Only visibility claims earn 12 October. Pending review 11, client location 10/supporting OAuth 9, continuity 8, CLI 7, public-ZIP 6, host 5, annotation 4, commerce 3, endpoint/recorder 2, checker 1 October and unrelated 29 September claims/conflicts retain their dates. Original Meeting Evidence 0.1.0/source/downloads, all 28 assets, existing widget/helper and 12 previous reports remain unchanged. Separate 33 checker and 49 recorder histories remain offline engineering evidence; ten actual-host cases remain NOT RUN, not a product-success rate or sample Codex-readiness proof.
Current Runtime input confirms 10 October published; the retained 11 October local candidate was a draft, not a receipt. This 12 October candidate is prepared locally, not accepted or published. Bounded documentary research is complete; actual host/creator/customer observations remain contingent on lawful supplied access. Stop further documentation-only visibility follow-ups absent consequential independent evidence or authorized contradictory actuals. Runtime browser/database/approvals/commit/delivery/publication remain separate host gates.