mcpbeat

CleanSlice MCP Server

io.github.CleanSlice/mcp
answering

CleanSlice is answering right now. Last checked 4 min ago. It exposes 4 tools. Last commit 24 Feb 2026.

Architecture docs and patterns for NestJS + Nuxt full-stack apps

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
241 ms
Response time
average over 24h
18
Stars
last commit 24 Feb 2026

Connect this server

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

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

categories
list-categories
List all available documentation categories. Use this to discover what categories are available before searching.
doc
read-doc
Read the full content of a specific document by path. Use this after `search` to get the complete document when snippets are not enough.
search
search
Search for relevant documentation. Use `list-categories` first to see available categories. Filter by query text, framework, phase, feature, category, or tags. Returns documents sorted by relevance.
started
get-started
⚠️ CRITICAL: request this tool first before creating any code! Returns essential slice creation rules. READ THIS FIRST before creating any slices! Contains the MOST IMPORTANT naming rule: ALWAYS use SINGULAR names (user/ not users/).

Endpoints

URLTransportStateLatencyChecked
https://mcp.cleanslice.org/mcp streamable-http answering 338 ms 4 min ago

CleanSlice — questions

Answers built from our own checks of this server.

What can CleanSlice do?
It exposes 4 tools, read directly from the server on our last check. Among them: get-started, list-categories, read-doc, search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is CleanSlice working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 241 ms. The bar chart above shows every period we have measured.
How do I connect CleanSlice?
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.
Does CleanSlice need an API key?
No. CleanSlice completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is CleanSlice?
It answers our handshake in 241 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is CleanSlice open source?
Yes — it is published under the MIT licence, written in TypeScript and 18 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.