Remote MCP · Endpoint
ai.yetty/yetty MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://mcp.yetty.ai/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- ai.yetty/yetty
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 36.8% from 19 checks
- Described by its publisher as
- Build, edit and run real hosted websites from your AI - content, SEO, menus, store, rollback.
- Website
- https://yetty.ai/
- Repository
- https://github.com/avniy/yetty-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 10 hours ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 13 days ago | Failed - the server returned an HTTP error | — |
| 16 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Handshake completed | 142 ms |
| 20 days ago | Handshake completed | 153 ms |
| 22 days ago | Handshake completed | 140 ms |
| 24 days ago | Handshake completed | 193 ms |
| 26 days ago | Handshake completed | 136 ms |
| 27 days ago | Handshake completed | 155 ms |
| 29 days ago | Handshake completed | 142 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 19 responding of 31.
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 ai.yetty/yetty and makes no claim about it beyond what these checks measured.