Submit or correct an MCP
Use the Submit an MCP form to propose a canonical source or report an incorrect source, publisher relationship, or use-case description. Do not include API keys, tokens, private configuration, or confidential data.
Security concern
Do not place exploit details, credentials, or private customer data in a public submission. Until a dedicated security inbox is published, provide only the public affected source URL and a high-level description through the submission route.
Accessibility and site feedback
Accessibility issues and factual site corrections can use the same submission route. Choose “Community or unknown” for publisher relationship and begin the use-case field with “Site feedback:” so the local review queue can distinguish the report.