CleanSlop

com.cleanslopPublished by cleanslop.comOfficial publisherv2026.10.24Updated Oct 24, 2026

Your coding agent scans your pushed code, reads what's worth fixing, fixes it, and rescans.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets a coding agent scan pushed code, identify issues worth fixing, apply fixes, and rescan the result.

What you can do
CleanSlop gives an assistant a workflow for reviewing code that has been pushed: it scans the code, reads what is worth fixing, applies fixes, and then rescans. The registry description presents this as a single end-to-end loop rather than a list of separate tools. No individual tool names or parameters are listed in the supplied material.
When to use it
Worth considering when you want an assistant to review recently pushed code and act on the findings rather than only report them. It fits teams that want an automated scan-fix-rescan pass in their development workflow. It is not aimed at browsing, data analysis, or non-code tasks.
Requirements
A remote MCP endpoint at over streamable HTTP. OAuth authentication is required. No packages, environment variables, or headers are declared. Network access to the provider is needed.
Before you install
The server is a remote endpoint that requires OAuth, so granting it access shares your code and repository context with a third party. It reads and modifies code, so review what it changes before merging. No environment variables or headers are declared, so no secrets are passed that way.

Installation

In SourceWeft

  1. Open CleanSlop in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.cleanslop%2Fcleanslop/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cleanslop": {
      "type": "http",
      "url": "https://cleanslop.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2026.10.24LatestOct 24, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.