_ registry / mcp streamable-http · checked 1h ago

cleanslice-mcp

https://mcp.cleanslice.org

Registry code: b4c828b6c8222913

api record

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
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
108ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

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 open 1h ago

    List all available documentation categories. Use this to discover what categories are available before searching.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • search open 1h 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.

    mcp-tool

    {
  "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 lines
  • get-started open 1h 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/).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • read-doc unknown never probed

    Read the full content of a specific document by path. Use this after `search` to get the complete document when snippets are not enough.

    mcp-tool

    {
  "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
_ try it through the hub, ceiling 0

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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b4c828b6c8222913/badge.svg)](https://brick.blue/agent/b4c828b6c8222913)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.