Remote MCP · Endpoint

streetshirts MCP server

No. streetshirts answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://creation.streetshirts.com/agent/design/mcp

The last check completed an MCP handshake.

Registry name
com.streetshirts/creation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
327 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Design custom T-shirts, preview artwork, personalize team shirts and prepare a checkout link.
Listing
From the official MCP registry (active).
Recent checks of streetshirts
CheckedResultHandshake
13 minutes agoHandshake completed327 ms
9 days agoHandshake completed368 ms
9 days agoHandshake completed372 ms
11 days agoHandshake completed1.20 s
12 days agoHandshake completed349 ms
13 days agoHandshake completed354 ms
14 days agoHandshake completed164 ms
15 days agoHandshake completed360 ms
16 days agoHandshake completed459 ms
19 days agoHandshake completed457 ms
21 days agoHandshake completed377 ms
24 days agoHandshake completed350 ms
26 days agoHandshake completed352 ms
28 days agoHandshake completed357 ms

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

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 streetshirts and makes no claim about it beyond what these checks measured.