Specification and documentation
Use the public VCP-Spec issue tracker for errors, unclear protocol wording, examples, and proposed amendments.
Open a specification issueFeedback and support
Send the right context to the right place
Include the page URL, visible version information, browser or runtime, and a concise reproduction. Do not place credentials, private context, personal data, or unreleased vulnerability details in a public report.
Report routes
SDK and implementation
Use the public VCP-SDK issue forms for reproducible implementation, package, CLI, WebMCP, and conformance defects.
Choose an SDK issue formAccessibility, privacy, or site feedback
Email a description and the affected page. Contact details are optional unless you want a reply.
Email the site teamSecurity
Keep suspected vulnerabilities private. The security policy explains safe reporting and the expected response process.
Read security.txtWhat to expect
Public reports are triaged by repository maintainers. Security reports follow the acknowledgement and severity targets in the security policy. This source candidate does not promise paid support, a service-level agreement, or continuous staffing.
Applies to VCP 3.1 source baseline and SDK 4.2.0 source candidate. Last reviewed 15 August 2026.