Remote MCP · Endpoint

Siteprint examples MCP server

No. Siteprint examples answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://siteprint.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.siteprint/examples
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Website designs as DESIGN.md: real Siteprint exports of Linear, Stripe, Ramp and Cal.com.
Listing
From the official MCP registry (active).
Recent checks of Siteprint examples
CheckedResultHandshake
1 hour agoHandshake completed124 ms
1 day agoHandshake completed108 ms
2 days agoHandshake completed174 ms
2 days agoHandshake completed121 ms
4 days agoHandshake completed370 ms
7 days agoHandshake completed86 ms
9 days agoHandshake completed87 ms
12 days agoHandshake completed151 ms
14 days agoHandshake completed144 ms
16 days agoHandshake completed100 ms
18 days agoHandshake completed181 ms
20 days agoHandshake completed129 ms
22 days agoHandshake completed104 ms
24 days agoHandshake completed83 ms
25 days agoHandshake completed97 ms

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

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