Contact / Send the useful details
Tell us what you were trying to do when the product got in the way
Send product feedback, support questions, security reports, partnership inquiries, or documentation corrections to the HTTPStatus team.
Working reference
What goes in, what comes out, and what the result can prove.
Concrete artifact
A useful technical report
Page: /mcp
Expected: OAuth discovery completes
Observed: client receives invalid_grant
Time: 2026-07-19T01:22:00Z
Client/version: [safe value]
Request ID: [redacted-safe identifier]
Secrets removed: yesReview sequence
Three checks before the result becomes a decision.
Reproduction
Include steps, expected result and observed result.
Environment
Name client, version and relevant time.
Safety
Remove credentials, private payloads and personal data.
Limits
What this workflow does not prove.
- Do not send active credentials or third-party exploit data.
- Security reports may require a restricted follow-up channel.
- Response time depends on severity, reproducibility and support scope.
Questions worth answering
Before you put it into a real workflow.
What should a bug report include?
The URL, steps, expected result, observed result, browser or client, and a safe sample if relevant.
How do I report a security issue?
Use a clear security subject and avoid including active credentials or exploit data that affects third parties.
Can I ask about enterprise use?
Yes. Include team size, intended workflows, security requirements, and your expected evaluation timeline.
Next move
Send the smallest safe reproduction that explains the problem.
A URL, expected behavior, observed behavior, and redacted sample are usually enough for the first reply.