
Official MCP RegistryListed
CleanApp
Report observed problems, approve handling, and track analysis decisions and action evidence.
First seen 13 Nov 2026. Evidence as of 16 Nov 2026.
5
Tools
From an anonymous probe
1
Source listings
Each with its own history
12
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| 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. | Read-only |
| 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 preview. New previews default to automatic publication/notices only after server eligibility and privacy checks. Disclose both permissions and obtain explicit approval; offer private/none when requested. Related observations are cluster candidates retaining independent evidence and attribution. Ask for missing place/product context; never infer location. Do not use for general discussion or emergency dispatch. | Read-only |
| 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 public links and cluster candidates. Poll only pending outcomes. A queued notice is not sent; a send is not read or fixed. Final means this cycle ended. Never search another user’s receipt or guess identifiers. | Read-only |
| 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. | Read-only |
| 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. Analysis not_required means AI analysis did not run for that cycle; explain the reason and next step. Older drafts retain their exact payload and permissions. A receipt is not a public report, sent notice or resolution. Reuse the same draft_token on retry. After timeout, check its tracking_token before retrying. | Destructive |
Change history
- cleanapp_submit_report: description changed (+"including any source context" +"publication/notice" +"frozen;")
- cleanapp_report_status: description changed (+"with" +"supplied" +"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.")
- cleanapp_prepare_report: input schema changed (+observed_at, +reporter_context, +source_platform, +source_published_at, +source_url, +submission_client)
- cleanapp_prepare_report: description changed (+"Prepare a factual" +"problem report" +"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 preview.")
- cleanapp_submit_report: input schema changed
- cleanapp_submit_report: description changed (+"cleanapp_prepare_report, its publication and notice permissions," +"Permissions are frozen in the draft; do not upgrade them at submission. Starts in private quarantine," +"receipt, and permits only the approved eligible actions after server checks. Older private drafts retain their original permissions. A receipt is not a")
- cleanapp_report_status: description changed (+"report-scoped recorded processing, decision/reason, public links when verified, cluster-candidate relationships" +"notice states with evidence. Poll this read-only tool for pending outcomes. Pending notices are not sent; a recorded send does" +"mean read")
- cleanapp_prepare_report: input schema changed (+handling, +requires_redaction)
- cleanapp_prepare_report: description changed (+"New previews default to automatic publication and responsible-party notices only after eligibility/privacy checks. Disclose both permissions in the exact preview and obtain explicit user approval before submission. Offer private review and no notices when requested. Related observations are cluster candidates with independent evidence and attribution, not dismissals.")
- server instructions changed (+"exact" +"its publication and notice permissions," +"Private review remains available and old drafts stay private. Treat related reports as cluster candidates and retain independent evidence and attribution. Use receipt outcomes to distinguish pending, held, failed and evidence-backed actions.")
- Description changed (registry)
- Listed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | io.github.cleanappio/cleanapp | 13 Nov 2026 | 16 Nov 2026 | 2 |