Bring the receipt. We’ll trace the boundary.
Start with the exact screen, query receipt, connector state, or MCP error. Never send an API key, access token, password, or raw private source record.
Account and sign-in
Use QueueProof sign in for a personal workspace. If authentication fails, include the time, browser, and visible error—but never a session cookie, authorization code, client secret, or screenshot containing private history.
Sources and retrieval
For connector help, include the provider name, QueueProof connector state, last proof time, and the non-secret connector ID. For an answer issue, include the QueueProof query receipt ID and expected fact, not the underlying private message or email.
ChatGPT, Codex, and Claude
Follow the Connect AI guide. Include the client name, exact MCP error, requested scope, and whether OAuth or a QueueProof-issued token was used. Revoke any credential that was accidentally exposed.
Contact the publisher
Contact the QueueProof publisher through the public GitHub profile. Include a short reproduction and the non-secret receipt identifiers above. Security-sensitive reports should describe impact without publishing exploit details.