# CleanApp Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## CleanApp

Report potholes, dumping, broken infrastructure or bad apps, and search what others have reported.

- Record: https://musedirectory.ai/connector/cleanapp
- Category: Lifestyle
- Developer: CleanApp (https://www.cleanapp.io/agents)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 695ms, checked 2026-11-13T19:21:30Z
- Endpoint: https://live.cleanapp.io/openai/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-13T19:21:30Z)
- Source: Found in the official MCP Registry (io.github.cleanappio/cleanapp) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.cleanappio%2Fcleanapp

Connects to CleanApp's public report network. Muse can search existing observations about potholes, litter, illegal dumping, accessibility barriers, pollution, software bugs and scams, then draft a factual report from your details and submit it to CleanApp's private review queue once you approve the preview.

Example request: "Report the dumped furniture on my street and check whether someone already flagged it."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use CleanApp to help me. It is a free service with an MCP server at https://live.cleanapp.io/openai/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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 exha
- cleanapp_prepare_report: Use this when the user wants to report an observed physical or digital problem: a pothole, dumped waste, unsafe infrastructure, accessibility barrier, pollution, software bug, suspected scam or service failure. Prepare a factual preview from user-provided details. No submission o
- cleanapp_submit_report: Use this only after the user approves the exact preview from cleanapp_prepare_report and sending it to CleanApp. Submits to CleanApp’s quarantine review lane and returns a private receipt. Not public publication, emergency dispatch, guaranteed routing or resolution. Reuse the sam
- cleanapp_report_status: Use this when the user asks what happened to their CleanApp submission and supplies the private tracking token returned for that report. Returns intake status and lane only, not proof of notification or resolution. Never search for another user’s receipt or guess identifiers.

Screening checks:
- MCP handshake: pass (Answered in 695ms)
- Domain against threat feeds (Cloudflare security DNS): pass (live.cleanapp.io, www.cleanapp.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (5 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)