CleanSlice
REMOTE · MCP.CLEANSLICE.ORG · SCANNED SEP 22
Architecture docs and patterns for NestJS + Nuxt full-stack apps
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 350 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the CleanSlice MCP server?
CleanSlice is a hosted endpoint at https://mcp.cleanslice.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.cleanslice.org
claude mcp add --transport http cleanslice-mcp 'https://mcp.cleanslice.org/mcp'
{
"mcpServers": {
"cleanslice-mcp": {
"url": "https://mcp.cleanslice.org/mcp"
}
}
} {
"servers": {
"cleanslice-mcp": {
"type": "http",
"url": "https://mcp.cleanslice.org/mcp"
}
}
} [mcp_servers.cleanslice-mcp] url = "https://mcp.cleanslice.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cleanslice-mcp": {
"type": "remote",
"url": "https://mcp.cleanslice.org/mcp",
"enabled": true
}
}
} openclaw mcp add cleanslice-mcp --url 'https://mcp.cleanslice.org/mcp' --transport streamable-http
mcp_servers:
cleanslice-mcp:
url: "https://mcp.cleanslice.org/mcp" {
"McpServers": {
"cleanslice-mcp": {
"Transport": "http",
"Url": "https://mcp.cleanslice.org/mcp"
}
}
} assistant mcp add cleanslice-mcp -t streamable-http -u 'https://mcp.cleanslice.org/mcp'
{
"mcpServers": {
"cleanslice-mcp": {
"type": "http",
"url": "https://mcp.cleanslice.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Tool coverage: 100 functional
- New tool “get-started” functional
- New tool “list-categories” functional
- New tool “read-doc” functional
- New tool “search” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://mcp.cleanslice.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.cleanslice.org | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9027c373c6044e2b0e481699ed2bcca1 |
| SANs: mcp.cleanslice.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cleanslice.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| cleanslice.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline' https://cdn.tailwindcss.com;script-src-attr 'unsafe-inline';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;font-src 'self' https://fonts.gstatic.com;img-src 'self' data:;connect-src 'self';base-uri 'self';form-action 'self';frame-ancestors 'self';object-src 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cleanslice.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cleanslice.org/mcp | HTTPS enforced | 301 | https://mcp.cleanslice.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get-started ~58
⚠️ 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/).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-categories ~26
List all available documentation categories. Use this to discover what categories are available before searching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read-doc ~48
Read the full content of a specific document by path. Use this after `search` to get the complete document when snippets are not enough.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Document path from search results |
No output schema declared.
No examples provided.
search ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category filter (e.g., quickstart, pattern, best-practices) |
| feature | string | – | Feature name (e.g., authentication, user-management, file-upload) |
| framework | string | – | Framework identifier (e.g., nestjs, nuxt) |
| limit | integer | – | Max results to return (default: 5) |
| offset | integer | – | Number of results to skip for pagination (default: 0) |
| phase | string | – | Development phase to filter by |
| query | string | – | Search query text (searches in document names, descriptions, and keywords) |
| sliceName | string | – | Name of the slice to find documentation for |
| tags | array | – | Array of tags to filter by |
| workingOn | string | – | Which application you are currently working on |
No output schema declared.
No examples provided.
What is the CleanSlice MCP server?
CleanSlice is an MCP server listed in the public MCP registry as io.github.CleanSlice/mcp. Architecture docs and patterns for NestJS + Nuxt full-stack apps. This page covers its hosted endpoint (https://mcp.cleanslice.org/mcp).
Is the CleanSlice MCP server safe to use?
CleanSlice scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CleanSlice MCP server expose?
CleanSlice exposes 4 tools: get-started, list-categories, search, read-doc. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Does the CleanSlice MCP server require authentication?
No. We connected to CleanSlice without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CleanSlice MCP server still maintained?
CleanSlice is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.