Remote MCP · Endpoint
Skew MCP server
No. Skew answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://skew.site/api/mcp
The last check completed an MCP handshake.
- Registry name
- site.skew/skew
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 101 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Authored design service: one-of-one landing pages, pitch decks, and research-grounded briefs.
- Website
- https://skew.site/
- Repository
- https://github.com/RayyanZahid/skew
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 101 ms |
| 1 day ago | Handshake completed | 111 ms |
| 2 days ago | Handshake completed | 122 ms |
| 3 days ago | Handshake completed | 128 ms |
| 4 days ago | Handshake completed | 132 ms |
| 5 days ago | Handshake completed | 120 ms |
| 6 days ago | Handshake completed | 143 ms |
| 8 days ago | Handshake completed | 204 ms |
| 11 days ago | Handshake completed | 145 ms |
| 13 days ago | Handshake completed | 148 ms |
| 15 days ago | Handshake completed | 134 ms |
| 18 days ago | Handshake completed | 168 ms |
| 20 days ago | Handshake completed | 208 ms |
| 22 days ago | Handshake completed | 161 ms |
| 24 days ago | Handshake completed | 192 ms |
| 26 days ago | Handshake completed | 160 ms |
| 27 days ago | Handshake completed | 127 ms |
| 29 days ago | Handshake completed | 119 ms |
| 29 days ago | Handshake completed | 119 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Skew and makes no claim about it beyond what these checks measured.