CleanSlice MCP server
online · 100% uptimeio.github.CleanSlice/mcp·v1.0.0·18 starsArchitecture docs and patterns for NestJS + Nuxt full-stack apps
18 stars
Reviews
Write oneNobody has reviewed CleanSlice yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
CleanSlice tools (4)
write = sends, deletes, buys or postsget-startedFree⚠️ 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/).
list-categoriesFreeList all available documentation categories. Use this to discover what categories are available before searching.
read-docFreeRead the full content of a specific document by path. Use this after `search` to get the complete document when snippets are not enough.
searchFreeSearch 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.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1661ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 16 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How CleanSlice compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 1,299 Productivity servers
- Tools
- 4
- the typical Productivity server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Productivity server answers 100%
- Response time
- 297 ms
- faster than 48% of 655 Productivity servers
- GitHub stars
- 18
- more than 82% of 854 Productivity servers
What its tools let an agent do: 4 read
Install CleanSlice in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://mcp.cleanslice.org/mcp
What the publisher says
From the CleanSlice repository's README, as published. We do not edit it. Read it on GitHub
CleanSlice MCP Server
MCP (Model Context Protocol) server that gives AI coding agents access to the CleanSlice architecture documentation. Connect it to Claude, Cursor, Windsurf, or any MCP-compatible client so the AI knows how to build apps using CleanSlice conventions.
Installation
Install in Claude Code
Run this command. See Claude Code MCP docs for more info.
claude mcp add --scope user --transport http cleanslice https://mcp.cleanslice.org/mcpRemove --scope user to install for the current project only.
Tip: enforce MCP usage with CLAUDE.md
To make sure Claude Code always consults the CleanSlice MCP before writing any code, add the following to your project's CLAUDE.md:
## CleanSlice MCP — Required
Before writing or modifying any code you MUST consult the CleanSlice MCP:
1. Call `get-started` to load the core architecture rules.
2. Call `list-categories` to see available documentation areas.
3. Call `search` with at least 2 task-relevant queries covering:
(a) core implementation details for the feature you are building,
(b) edge cases, constraints, or standards that apply.
4. Call `read-doc` to read the full document when search snippets aren't enough.
Do NOT guess conventions — always verify against MCP results first.This ensures the agent reads CleanSlice docs at the start of every task, not after the fact.
Optional: add a Stop hook as a safety net
To catch cases where the agent skips the MCP despite the CLAUDE.md instruction, add this to .claude/settings.json:
{
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "agent",
"timeout": 180,
"prompt": "You are a verification subagent. Your job: ensure the main Claude Code agent used the `cleanslice` MCP knowledge sufficiently and did not guess.\n\nContext JSON:\n$ARGUMENTS\n\nVerification requirements:\n1) Identify what the user asked for (deliverables + constraints) from the conversation/transcript in $ARGUMENTS.\n2) Verify the agent consulted the `cleanslice` MCP server for relevant knowledge BEFORE finalizing:\n - Must call `cleanslice` \"get-started\" at least once (or equivalent) to confirm the server's purpose and usage.\n - Must call \"list-categories\" to understand the available knowledge areas.\n - Must call \"search\" with task-relevant queries (at least 2 searches) covering: (a) core implementation details, (b) edge cases / constraints.\n - May call \"read-doc\" to get full document content when search snippets are insufficient.\n3) Validate coverage:\n - If any required category is relevant but not checked, fail.\n - If answers include specifics that are not supported by MCP results, fail.\n4) Output STRICT JSInstall in Cursor
Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
CleanSlice: common questions
- Is CleanSlice MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the CleanSlice safety report
- How do I install CleanSlice?
- It runs remotely at mcp.cleanslice.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does CleanSlice need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is CleanSlice maintained?
- The last commit was 53 days ago (2026-09-12). The latest release is v1.0.0.
- Is CleanSlice up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of CleanSlice?
- Servers from other publishers that do the same job: Context7 MCP server, Argent MCP server and Svelte MCP server.
- How does CleanSlice compare with other Productivity MCP servers?
- safety score 89/100 (higher than 80% of 1,299 Productivity servers); tools 4 (the typical Productivity server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to CleanSlice
Same job from other publishers: the closest match first, then the best rated.
Context7Up-to-date docs for AI agentsnot reviewedWidely usedA- ArgentDrive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agentnot reviewedWidely usedA
- Svelte MCPThe official Svelte MCP server providing docs and autofixing tools for Svelte developmentnot reviewedEstablishedA
SvGridChecks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.not reviewedEstablishedA- Coolify46 optimized tools for managing Coolify infrastructure, diagnostics, and docs searchnot reviewedEstablishedB