Remote MCP · Endpoint
Website Launch MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://instant-website-builder-usa-6feac193.base44.app/functions/websiteServiceMcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.jgaethle10/website-launch
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- Business website planning and launch assistance with human-confirmed next steps.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 365 ms |
| 4 days ago | Handshake completed | 725 ms |
| 6 days ago | Handshake completed | 193 ms |
| 7 days ago | Handshake completed | 351 ms |
| 9 days ago | Handshake completed | 205 ms |
| 10 days ago | Handshake completed | 279 ms |
| 11 days ago | Handshake completed | 422 ms |
| 14 days ago | Handshake completed | 224 ms |
| 15 days ago | Handshake completed | 395 ms |
| 17 days ago | Handshake completed | 353 ms |
| 19 days ago | Handshake completed | 347 ms |
| 20 days ago | Handshake completed | 374 ms |
| 21 days ago | Handshake completed | 472 ms |
| 22 days ago | Handshake completed | 534 ms |
| 22 days ago | Handshake completed | 334 ms |
| 23 days ago | Handshake completed | 458 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 Website Launch and makes no claim about it beyond what these checks measured.