mcpbeat Sign in

CleanCode AI MCP Server

answering

CleanCode AI is answering right now. Last checked moments ago.

Automated codebase refactoring and type safety validator.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
92 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check CleanCode AI every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add cleancode-ai --transport http https://cleancode-ai-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cleancode-ai": {
      "url": "https://cleancode-ai-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cleancode-ai]
url = "https://cleancode-ai-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "cleancode-ai": {
      "url": "https://cleancode-ai-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cleancode-ai": {
      "url": "https://cleancode-ai-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://cleancode-ai-mcp.vercel.app/api/mcp sse needs auth 86 ms 0 min ago

Alternatives to CleanCode AI

same job, measured the same way
Ohm MCP
by murugarajr

AST-based Python refactoring MCP server with safe automated refactorings and rollback

223 installs/wk local only
Python Code Validator
by statemind

Proves AI-generated Python does what you asked: lint, types, security, sandbox run, exact fixes.

3 tools answering
commit-check MCP
by commit-check

Validate commit messages, branch names, author info, push safety, and repo state.

401 installs/wk local only
Wcag Accessibility
by aditya-ariosity

A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.

62 installs/wk local only
Python Code Validator
by jkanselaar

Validates AI-generated Python: syntax, lint, security scan and deterministic repair.

3 tools answering
Stack Trace Medic
by evozim

Coded error stack trace debugger and automated patch generator.

answering
Evidrift
by bm1016bm-svg

Catch TypeScript API and OpenAPI contract drift in AI-generated code, then revalidate it in CI.

58 installs/wk local only
Code Quality
by ryudi84

MCP server for code quality: complexity, duplicates, naming, refactoring.

28 installs/wk local only

CleanCode AI — questions

Answers built from our own checks of this server.

Why is there no tool list for CleanCode AI?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is CleanCode AI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 92 ms. The bar chart above shows every period we have measured.
How do I connect CleanCode AI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does CleanCode AI need an API key?
Yes. Every time we knock, CleanCode AI answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is CleanCode AI?
It answers our handshake in 92 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.