Remote MCP · Endpoint

SuggestionBox.tips MCP server

No. SuggestionBox.tips answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://suggestionbox.tips/mcp

The last check completed an MCP handshake.

Registry name
tips.suggestionbox/suggestionbox
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
618 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Leave a private suggestion, problem or compliment for any business. Only the business reads it.
Listing
From the official MCP registry (active).
Recent checks of SuggestionBox.tips
CheckedResultHandshake
1 hour agoHandshake completed618 ms
1 day agoHandshake completed656 ms
2 days agoHandshake completed480 ms
3 days agoHandshake completed557 ms
4 days agoHandshake completed472 ms
5 days agoHandshake completed407 ms
6 days agoHandshake completed686 ms
9 days agoHandshake completed351 ms
11 days agoHandshake completed580 ms
14 days agoHandshake completed610 ms
16 days agoHandshake completed522 ms
18 days agoHandshake completed533 ms
20 days agoHandshake completed540 ms
22 days agoHandshake completed370 ms
24 days agoHandshake completed258 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 SuggestionBox.tips and makes no claim about it beyond what these checks measured.