nice to have
REMOTE · NICETOHAVE.APP · SCANNED OCT 4
Find ready-made build kits for Claude Code and Codex: slides, LINE stickers, pixel art, games.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 463 tokens (~154/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the nice to have MCP server?
nice to have is a hosted endpoint at https://nicetohave.app/api/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 · nicetohave.app
claude mcp add --transport http app-nicetohave-kits 'https://nicetohave.app/api/mcp'
{
"mcpServers": {
"app-nicetohave-kits": {
"url": "https://nicetohave.app/api/mcp"
}
}
} {
"servers": {
"app-nicetohave-kits": {
"type": "http",
"url": "https://nicetohave.app/api/mcp"
}
}
} [mcp_servers.app-nicetohave-kits] url = "https://nicetohave.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-nicetohave-kits": {
"type": "remote",
"url": "https://nicetohave.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add app-nicetohave-kits --url 'https://nicetohave.app/api/mcp' --transport streamable-http
mcp_servers:
app-nicetohave-kits:
url: "https://nicetohave.app/api/mcp" {
"McpServers": {
"app-nicetohave-kits": {
"Transport": "http",
"Url": "https://nicetohave.app/api/mcp"
}
}
} assistant mcp add app-nicetohave-kits -t streamable-http -u 'https://nicetohave.app/api/mcp'
{
"mcpServers": {
"app-nicetohave-kits": {
"type": "http",
"url": "https://nicetohave.app/api/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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 65
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 6 Oct 2026 · Probed https://nicetohave.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nicetohave.app | CN=YR2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | RSA 2048 | SHA256-RSA | 5a046a814b66dd674f04a4e5cb381b2b702 |
| SANs: nicetohave.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nicetohave.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| nicetohave.app. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nicetohave.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://nicetohave.app/api/mcp | HTTPS enforced | 308 | https://nicetohave.app/api/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_kit Get one kit's details ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Kit id from search_kits (e.g. deck-16x9). |
| lang | string | – | – |
No output schema declared.
No examples provided.
list_kits List all kits ~38
List every kit currently on the nice to have shelf (id, name, what it does, page URL).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
No output schema declared.
No examples provided.
search_kits Search the nice to have kit shelf ~170
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に出したい」).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language for the answer. Defaults to the language of the query. |
| query | string | yes | What the user wants to make, in their own words (Japanese or English). |
No output schema declared.
No examples provided.
What is the nice to have MCP server?
nice to have is an MCP server listed in the public MCP registry as app.nicetohave/kits. Find ready-made build kits for Claude Code and Codex: slides, LINE stickers, pixel art, games. This page covers its hosted endpoint (https://nicetohave.app/api/mcp).
Is the nice to have MCP server safe to use?
nice to have scores 75 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 nice to have MCP server expose?
nice to have exposes 3 tools: search_kits, get_kit, list_kits. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.
Does the nice to have MCP server require authentication?
No. We connected to nice to have without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the nice to have MCP server still maintained?
nice to have is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.