Remote MCP · Endpoint

SuppCo MCP server

No. SuppCo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.supp.co/mcp

The last check completed an MCP handshake.

Registry name
co.supp/suppco
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
30 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Supplement research, product and brand TrustScores, and your SuppCo stack and Buying Club cart.
Website
https://supp.co/developers
Listing
From the official MCP registry (active).
Recent checks of SuppCo
CheckedResultHandshake
1 hour agoHandshake completed79 ms
17 hours agoHandshake completed108 ms
1 day agoHandshake completed114 ms
3 days agoFailed - the request timed out—
5 days agoHandshake completed147 ms
7 days agoHandshake completed82 ms
10 days agoHandshake completed132 ms
12 days agoHandshake completed57 ms
14 days agoHandshake completed67 ms
16 days agoHandshake completed71 ms
18 days agoHandshake completed64 ms
20 days agoHandshake completed53 ms
22 days agoHandshake completed58 ms
23 days agoHandshake completed78 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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