Remote MCP · Endpoint
Heista MCP server
No — it is up, but it requires credentials. Heista answered 9 hours ago with an authentication challenge rather than a session.
Auth requiredLast checked 9 hours ago
Server URL
https://www.heista.co/api/mcp/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- co.heista/api
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 118 tools
- Uptime, last 30 days
- 94.1% from 17 checks
- Described by its publisher as
- Decode video ads, load brand intelligence, generate ad scripts.
- Website
- https://www.heista.co/
- Repository
- https://github.com/Heista-co/heista-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 9 hours ago | Credentials required | — |
| 2 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
| 5 days ago | Credentials required | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 8 days ago | Credentials required | — |
| 9 days ago | Credentials required | — |
| 12 days ago | Credentials required | — |
| 13 days ago | Handshake completed | 546 ms |
| 15 days ago | Handshake completed | 475 ms |
| 16 days ago | Handshake completed | 629 ms |
| 17 days ago | Handshake completed | 515 ms |
| 19 days ago | Handshake completed | 4.55 s |
| 19 days ago | Handshake completed | 658 ms |
| 20 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
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 Heista and makes no claim about it beyond what these checks measured.