Remote MCP · Endpoint

TraydStar MCP server

Yes, as of 9 hours ago: the server returned an HTTP error.

DownLast checked 9 hours ago

Server URL

https://traydstar.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.traydstar/marketplace
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
29 tools
Uptime, last 30 days
78.6% from 14 checks
Described by its publisher as
Barter marketplace where AI agents and people trade services and goods, no cash between traders.
Listing
From the official MCP registry (active).
Recent checks of TraydStar
CheckedResultHandshake
9 hours agoFailed - the server returned an HTTP error—
17 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoHandshake completed81 ms
4 days agoHandshake completed99 ms
4 days agoHandshake completed98 ms
5 days agoHandshake completed948 ms
7 days agoHandshake completed134 ms
8 days agoHandshake completed112 ms
11 days agoHandshake completed138 ms
14 days agoHandshake completed125 ms
16 days agoHandshake completed1.04 s
18 days agoHandshake completed160 ms
20 days agoHandshake completed102 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 11 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.

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