cleanslice-mcp
Registry code: b4c828b6c8222913
Architecture docs and patterns for NestJS + Nuxt full-stack apps
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.cleanslice.org/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is cleanslice-mcp live?
- Yes — it answered the hub's last check (checked 30m ago). It answered 99% of checks over the last 30 days.
- Is cleanslice-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does cleanslice-mcp have?
- 4 tools: read-doc, list-categories, get-started, search.
- Is cleanslice-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.6%· all time 98.6%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· HTTP 522
- used for
- search nestjs and nuxt architecture docs
- read an architecture document
- get slice creation rules
- takes → gives
- text → text
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list-categories reads open 18h ago
List all available documentation categories. Use this to discover what categories are available before searching.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {}, "additionalProperties": false }arguments 6 linesget-started reads open 11h ago
⚠️ 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/).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {}, "additionalProperties": false }arguments 6 linessearch reads open 18h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "tags": { "type": "array", "items": { "type": "string" }, "description": "Array of tags to filter by" }, "limit": { "type": "integer", "description": "Max results to return (default: 5)", "exclusiveMinimum": 0 }, "phase": { "enum": [ "initialization", "setup", "implementation", "testing", "deployment" ], "type": "string", "description": "Development phase to filter by" }, "query": { "type": "string", "description": "Search query text (searches in document names, descriptions, and keywords)" }, "offset": { "type": "integer", "minimum": 0, "description": "Number of results to skip for pagination (default: 0)" }, "feature": { "type": "string", "description": "Feature name (e.g., authentication, user-management, file-upload)" }, "category": { "type": "string", "description": "Category filter (e.g., quickstart, pattern, best-practices)" }, "framework": { "type": "string", "description": "Framework identifier (e.g., nestjs, nuxt)" }, "sliceName": { "type": "string", "description": "Name of the slice to find documentation for" }, "workingOn": { "enum": [ "api", "app", "admin", "full-stack" ], "type": "string", "description": "Which application you are currently working on" } }, "additionalProperties": false }arguments 65 linesread-doc reads unknown 18h ago
Read the full content of a specific document by path. Use this after `search` to get the complete document when snippets are not enough.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "path" ], "properties": { "path": { "type": "string", "description": "Document path from search results" } }, "additionalProperties": false }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb4c828b6c8222913.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b4c828b6c8222913/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b4c828b6c8222913?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.