Remote MCP · Endpoint

NutsGrowth MCP server

No. NutsGrowth answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://nutsgrowth.com/mcp

The last check completed an MCP handshake.

Registry name
com.nutsgrowth/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
485 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Startup and SaaS tools and their alternatives, with prices and when a person last checked them.
Listing
From the official MCP registry (active).
Recent checks of NutsGrowth
CheckedResultHandshake
56 minutes agoHandshake completed485 ms
3 days agoHandshake completed157 ms
12 days agoHandshake completed179 ms
13 days agoHandshake completed162 ms
14 days agoHandshake completed194 ms
15 days agoHandshake completed153 ms
17 days agoHandshake completed169 ms
18 days agoHandshake completed143 ms
18 days agoHandshake completed129 ms
20 days agoHandshake completed222 ms
22 days agoHandshake completed140 ms
25 days agoHandshake completed430 ms
27 days agoHandshake completed185 ms
29 days agoHandshake completed219 ms

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

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 NutsGrowth and makes no claim about it beyond what these checks measured.