CleanApp status
Answered our latest tool-list check 3 hours ago with 5 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 06:15 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 06:15 | Answered | 2.7 s | 5 |
| 16 Nov, 06:15 | Answered | 2.5 s | 5 |
Tools (5)
Read from the server on 17 Nov 2026.
- cleanapp_open
- Use this when the user wants to open CleanApp, report a real-world or digital problem, or browse the CleanApp miniapp. Do not use for household cleaning advice or computer disk-cleaning tasks.
- cleanapp_search_reports
- Use this when the user wants existing CleanApp observations about potholes, litter, illegal dumping, accessibility barriers, infrastructure damage, pollution, software bugs, scams or service problems. The brand need not be mentioned. Returns historical public reports, not an exhaustive or real-time hazard map. Do not use for generic advice, emergency dispatch or private records.
- cleanapp_prepare_report
- Prepare a factual physical or digital problem report from user-provided details. No report is submitted. Include optional source platform/URL, observation and source-publication times, reporter context or submitting AI client only when explicitly supplied; do not infer them from the affected product, fill unknown times, or harvest private chats. Show all supplied context in the exact approval prev
- cleanapp_submit_report
- Use this only after the user approves the exact preview from cleanapp_prepare_report, including any source context and publication/notice permissions, and sending it to CleanApp. Permissions are frozen; do not upgrade them. Starts in private quarantine and returns a receipt. Report the recorded outcome precisely: held means received but blocked, not successful publication or notice delivery. Analy
- cleanapp_report_status
- Use this with the private tracking token supplied for the user’s submission. Distinguish intake received, AI analysis, decision/reason, publication and notice evidence. Say received but blocked when held; do not call a held report successfully published, notified or resolved. Explain not_required as AI analysis not run and give the recorded reason and next step. Returns report-scoped verified publ