Remote MCP · Endpoint

ThriveCart MCP Server and API by Cotlet MCP server

Yes, as of 5 hours ago: the check failed for an unclassified reason.

DownLast checked 5 hours ago

Server URL

https://cotlet.dev/mcp/v1/thrivecart/connect

The last check failed: the check failed for an unclassified reason.

Registry name
dev.cotlet/thrivecart
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
ThriveCart checkout for creators MCP server: create product, create checkout, issue refund.
Listing
From the official MCP registry (active).
Recent checks of ThriveCart MCP Server and API by Cotlet
CheckedResultHandshake
5 hours agoFailed - the check failed for an unclassified reason—
4 days agoFailed - the check failed for an unclassified reason—
7 days agoFailed - the check failed for an unclassified reason—

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

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 ThriveCart MCP Server and API by Cotlet and makes no claim about it beyond what these checks measured.