Remote MCP · Endpoint

nice to have MCP server

No. nice to have answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nicetohave.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.nicetohave/kits
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
5 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Find ready-made build kits for Claude Code and Codex: slides, LINE stickers, pixel art, games.
Listing
From the official MCP registry (active).
Recent checks of nice to have
CheckedResultHandshake
1 hour agoHandshake completed79 ms
2 days agoHandshake completed121 ms
4 days agoHandshake completed120 ms
6 days agoHandshake completed75 ms
8 days agoHandshake completed74 ms
10 days agoHandshake completed66 ms
11 days agoHandshake completed64 ms
13 days agoHandshake completed89 ms
14 days agoHandshake completed137 ms
15 days agoHandshake completed101 ms
18 days agoHandshake completed57 ms
19 days agoHandshake completed63 ms
21 days agoHandshake completed103 ms
22 days agoFailed - the hostname does not resolve—
23 days agoHandshake completed230 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with nice to have and makes no claim about it beyond what these checks measured.