CleanApp MCP server
io.github.cleanappio/cleanappcleanappiostreamable-httpv1.1.0Scanned
Report observed problems, approve handling, and track analysis decisions and action evidence.
5 tools: 1 can delete or cancel things, 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CleanApp MCP server can do
The CleanApp MCP server is published by the GitHub account cleanappio. It has 5 tools. It can delete or cancel things (1 tool: cleanapp_submit_report) and create or change data (2 tools: cleanapp_open and cleanapp_prepare_report). 2 tools only read.
5 tools bring in text other people can write (cleanapp_open, cleanapp_search_reports, cleanapp_prepare_report and 2 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Deletes or cancels 1Claude Code: deny
cleanapp_submit_reportUse this only after the user approves the exact preview from cleanapp_prepare_report, its publication and notice permissions, and sending it to CleanApp.Reads text others writeNo findings
Why it is in this group
- The name "cleanapp_submit_report" says "submit": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this only after the user approves the exact preview from cleanapp_prepare_report, its publication and notice permissions, and sending it to CleanApp. Permissions are frozen in the draft; do not upgrade them at submission. Starts in private quarantine, returns a private receipt, and permits only the approved eligible actions after server checks. Older private drafts retain their original permissions. A receipt is not a public report, sent notice or resolution. Reuse the same draft_token on retry. After timeout, check the returned tracking_token before retrying.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
- idempotentHint: true
Changes things 2Claude Code: ask
cleanapp_openUse this when the user wants to open CleanApp, report a real-world or digital problem, or browse the CleanApp miniapp.Reads text others write1 finding
Why it is in this group
- The name "cleanapp_open" says "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "cleanapp_open" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "cleanapp_open" says "open": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
cleanapp_prepare_reportUse this when the user wants to report an observed physical or digital problem: a pothole, dumped waste, unsafe infrastructure, accessibility barrier, pollution, software bug, susp…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. 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. No submission occurs. Ask for the affected place or product if missing; never infer precise location. Do not use for general discussion or emergency dispatch.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
Only reads 2Show 2 read-only tools
cleanapp_report_statusUse this when the user asks what happened to their CleanApp submission and supplies the private tracking token returned for that report.Reads text others writeNo findings
Why it is in this group
- The name "cleanapp_report_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this when the user asks what happened to their CleanApp submission and supplies the private tracking token returned for that report. Returns report-scoped recorded processing, decision/reason, public links when verified, cluster-candidate relationships and notice states with evidence. Poll this read-only tool for pending outcomes. Pending notices are not sent; a recorded send does not mean read or fixed. Final means the processing cycle ended, not issue resolution. Never search for another user’s receipt or guess identifiers.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
cleanapp_search_reportsUse this when the user wants existing CleanApp observations about potholes, litter, illegal dumping, accessibility barriers, infrastructure damage, pollution, software bugs, scams …Reads text others writeNo findings
Why it is in this group
- The name "cleanapp_search_reports" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://live.cleanapp.io/openai/mcp: tools/list returned 5 tools to an anonymous client, including cleanapp_submit_report (destructive), cleanapp_open (write), cleanapp_prepare_report (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncleanapp_open
The server marks "cleanapp_open" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "cleanapp_open" says "open": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:cleanapp_prepare_reportChanges thingsdescriptioninputSchema
- Changed:cleanapp_report_statusOnly readsdescription
- Changed:cleanapp_submit_reportDeletes or cancelsdescriptioninputSchema
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cleanapp https://live.cleanapp.io/openai/mcpclaude mcp add --transport http cleanapp https://live.cleanapp.io/openai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cleanapp__cleanapp_search_reports",
"mcp__cleanapp__cleanapp_report_status"
],
"ask": [
"mcp__cleanapp__cleanapp_open",
"mcp__cleanapp__cleanapp_prepare_report"
],
"deny": [
"mcp__cleanapp__cleanapp_submit_report"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cleanapp. Review it before you use it.
Capability tags behind 5 rules
- mcp__cleanapp__cleanapp_open untrusted-input
- mcp__cleanapp__cleanapp_search_reports untrusted-input
- mcp__cleanapp__cleanapp_prepare_report untrusted-input
- mcp__cleanapp__cleanapp_submit_report untrusted-input
- mcp__cleanapp__cleanapp_report_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cleanappio/cleanapp/verify?hash=8323caa61dbb02a655d65e0a6b9949e0de0486461a1d45860840fc22ed9205a8" | jq -e '.changed == false'Pinned hash 8323caa61dbb, from Nov 14, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.cleanappio/cleanapp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.cleanappio/cleanapp)Source: MCP Registry. Synced Nov 14, 2026, 17:18 UTC.
CleanApp MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CleanApp MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CleanApp MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cleanapp_submit_report.
Can the CleanApp MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CleanApp MCP server have?
- 5 tools: 1 destructive, 2 write, 2 read. cleanapp_submit_report, cleanapp_open, cleanapp_prepare_report, cleanapp_search_reports and cleanapp_report_status.
Does the CleanApp MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CleanApp MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CleanApp MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.