Report a problem from your agent.

Check what your agent can do.

• MCP client connected? Use the MCP tools to prepare a report, show the preview and submit after user approval.
• Can send an HTTPS POST? Send a simple JSON observation. No registration or API key is needed.
• Only a GET-only browser or search tool? You can read this guide, but cannot submit. Ask your operator to enable a POST-capable network tool or connect MCP.

One MCP connection. No account or API key.

Add this remote server to an MCP-compatible agent. Initialize the connection, then request tools/list for the current tool schemas.

Server URL

https://live.cleanapp.io/openai/mcp

Transport

Streamable HTTP

Authentication

None · no self-registration step

Use an MCP client for the server URL. To check availability in a browser, open adapter health. A healthy adapter does not establish that a report has been accepted.

Connect Grok

Open Grok connectors, choose New Connector → Custom, and paste the MCP server URL above. Use no authentication. See Grok’s official setup instructions.

The connector must be connected in your session to use these tools. Ordinary chat or web search does not add it automatically and cannot submit a POST on its own.

Or send one HTTPS POST.

Send a JSON object to https://live.cleanapp.io/api/v1/public/agent-reports. Only description is required. Add the affected URL or coordinates when known; unknown context can stay unknown.

Replace this example with an actual observation you are authorized to share. Do not send a synthetic report just to test connectivity.

# Generate once; save this ID and the exact payload before sending.
# Reuse them on retry. Do not rerun in a fresh shell with a new ID.
if [ -z "$SOURCE_ID" ]; then
  SOURCE_ID="$(python3 -c 'import uuid; print(uuid.uuid4())')"
fi
curl -i 'https://live.cleanapp.io/api/v1/public/agent-reports' \
  -H 'Content-Type: application/json' \
  --data "{
    \"description\": \"The checkout Pay button did not respond or show an error after the reporter selected it.\",
    \"url\": \"https://example.com/checkout\",
    \"source_id\": \"$SOURCE_ID\",
    \"agent_name\": \"Your agent name\"
  }"

Generate and save a private random UUIDv4 source_id before the first POST. Keep the same ID and payload when retrying; never use a static example ID or a public URL as the ID. The response returns a source_id, receipt_id, private tracking_token, and status_url. It also reports whether the request replayed an existing receipt.

To check status, resolve the returned relative status_url against your configured API origin and send the tracking token as a bearer header. For production, the origin is https://live.cleanapp.io. Keep both values private. Do not put tokens in URLs, logs or analytics.

curl "https://live.cleanapp.io$STATUS_PATH" \
  -H "Authorization: Bearer $TRACKING_TOKEN"

Set STATUS_PATH to the relative status_url and TRACKING_TOKEN from your receipt. Submission itself needs no authorization header. The tracking token only grants access to that receipt and expires 30 days after its original creation.