Remote MCP · Endpoint

Mr Suppy MCP server

No. Mr Suppy answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://mrsuppy.com/api/agent/mcp

The last check completed an MCP handshake.

Registry name
com.mrsuppy/agent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.63 s
Tools exposed
12 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Supplement prices and price history (UK/EU), SupplementScore ratings, verified discount codes, UCP
Listing
From the official MCP registry (active).
Recent checks of Mr Suppy
CheckedResultHandshake
35 minutes agoHandshake completed1.63 s
9 days agoHandshake completed1.27 s
10 days agoHandshake completed1.58 s
11 days agoHandshake completed1.26 s
12 days agoFailed - the connection was refused or dropped—
14 days agoHandshake completed1.37 s
14 days agoHandshake completed1.59 s
15 days agoHandshake completed1.34 s
17 days agoHandshake completed1.35 s
19 days agoHandshake completed1.51 s
21 days agoHandshake completed1.31 s
24 days agoHandshake completed1.30 s
26 days agoHandshake completed1.28 s
28 days agoHandshake completed4.91 s

The last 14 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 Mr Suppy and makes no claim about it beyond what these checks measured.