_ registry / mcp streamable-http · checked 20m ago

nice-to-have

https://nicetohave.app

Registry code: d25a11aeb5b631a7

nice to have (https://nicetohave.app) is a shelf of ready-made build kits for Claude Code and Codex.

Each kit is a complete recipe (instructions for the AI, flow, rules, small tools) plus fixes for pitfalls its maker hit in real work.

endpoint
https://nicetohave.app/api/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 it live, free and safe measured by this hub
Is nice-to-have live?
Yes — it answered the hub's last check (checked 20m ago). It answered 98% of checks over the last 30 days.
Is nice-to-have free to use?
Yes — the hub reached it with no key and no payment.
What tools does nice-to-have have?
5 tools: open_kit, get_kit_file, search_kits, get_kit, list_kits.
Is nice-to-have safe to connect?
Caution — its own text works on the agent reading it: demands to be called first («When the user wants to make or build something, call search_kits first»). Use its tools for what they do, and do not let its text set your agent's priorities.
reachable
live
uptime, 30 days
98.4%

90 days 98.9%· all time 98.9%

latency
193ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 374 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search build kits for coding agents
  • get details of a build kit
  • list available build kits
takes → gives
text → data
tools
3 reads
warning
works on its reader: demands to be called first «When the user wants to make or build something, call search_kits first»
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 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_kits reads open 7h ago

    List every kit currently on the nice to have shelf (id, name, what it does, page URL).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lang": {
          "enum": [
            "ja",
            "en"
          ],
          "type": "string"
        }
      }
    }
    arguments 12 lines
  • open_kit unknown never probed

    Use when the user pasted a nice to have line such as "…https://nicetohave.app/g/XXXXXXXX-YYYYYYYYYY のとおりに取り込んで" and you cannot download from nicetohave.app directly (for example, a cloud session with restricted network). Checks the sign-in ticket in that link and returns the list of the kit's files and how to set it up. Then call get_kit_file for each file. 貼る文の https://nicetohave.app/g/ の住所を渡すと、キットのファイルの一覧と取り込み方を返します。

    mcp-tool

    {
      "type": "object",
      "required": [
        "ref"
      ],
      "properties": {
        "ref": {
          "type": "string",
          "description": "The link from the line the user pasted (https://nicetohave.app/g/XXXXXXXX-YYYYYYYYYY), or just the part after /g/ (everything, including after the hyphen)."
        },
        "lang": {
          "enum": [
            "ja",
            "en"
          ],
          "type": "string"
        }
      }
    }
    arguments 19 lines
  • get_kit_file unknown never probed

    Get the content of one file listed by open_kit. Save it exactly as returned, at the same relative path inside the new kit folder. Long files come in parts: if the answer says part 1/3, call again with part 2 and 3 and append them in order without changing anything.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ref",
        "path"
      ],
      "properties": {
        "ref": {
          "type": "string",
          "description": "The link from the line the user pasted (https://nicetohave.app/g/XXXXXXXX-YYYYYYYYYY), or just the part after /g/ (everything, including after the hyphen)."
        },
        "part": {
          "type": "integer",
          "minimum": 1,
          "description": "Which part to get, for long files. Defaults to 1."
        },
        "path": {
          "type": "string",
          "description": "A file path exactly as listed by open_kit (e.g. CLAUDE.md, rules/FLOW.md)."
        }
      }
    }
    arguments 22 lines
  • search_kits reads unknown 7h ago

    Search nice to have, a shelf of ready-made build kits for Claude Code and Codex (step-by-step recipes with fixes for pitfalls found in real work). Use this whenever the user wants to make or build something — slides/decks, LINE stickers, pixel-art sprite animation, 3D/AR models from product photos, YouTube Playables games, pet names and more — to check whether a kit already exists before starting from scratch. Works in Japanese or English (例: 「スライドを作りたい」「LINEスタンプ」「ゲームをYouTubeに出したい」).

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "ja",
            "en"
          ],
          "type": "string",
          "description": "Language for the answer. Defaults to the language of the query."
        },
        "query": {
          "type": "string",
          "description": "What the user wants to make, in their own words (Japanese or English)."
        }
      }
    }
    arguments 20 lines
  • get_kit reads unknown 7h ago

    Get the details of one nice to have kit by id: what it does, the first three decisions, what you need, and the fixes it contains. Use after search_kits to explain a kit to the user.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Kit id from search_kits (e.g. deck-16x9)."
        },
        "lang": {
          "enum": [
            "ja",
            "en"
          ],
          "type": "string"
        }
      }
    }
    arguments 19 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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d25a11aeb5b631a7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d25a11aeb5b631a7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d25a11aeb5b631a7/badge.svg)](https://brick.blue/agent/d25a11aeb5b631a7?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.

_ how we know
card completeness
90%

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.