Remote MCP · Endpoint

Shiped MCP server

No. Shiped answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://shiped.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.kandahk/shiped
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.99 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Deploy AI-generated HTML/CSS/JS to instant public HTTPS URLs from any MCP-compatible agent.
Listing
From the official MCP registry (active).
Recent checks of Shiped
CheckedResultHandshake
1 hour agoHandshake completed2.99 s
2 days agoHandshake completed170 ms
4 days agoHandshake completed302 ms
5 days agoHandshake completed251 ms
7 days agoHandshake completed418 ms
8 days agoHandshake completed698 ms
9 days agoHandshake completed291 ms
12 days agoHandshake completed288 ms
13 days agoHandshake completed234 ms
15 days agoHandshake completed334 ms
17 days agoHandshake completed378 ms
18 days agoHandshake completed239 ms
19 days agoHandshake completed236 ms
20 days agoHandshake completed364 ms
20 days agoHandshake completed228 ms
21 days agoHandshake completed206 ms
23 days agoHandshake completed399 ms

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

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