Remote MCP · Endpoint
Computer-Use Agents API MCP server
No. Computer-Use Agents API answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://agp.eu.hcompany.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.hcompai/hai-agents
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 274 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Run and manage H Company's Computer-Use Agents from any MCP client.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 274 ms |
| 1 day ago | Handshake completed | 282 ms |
| 2 days ago | Handshake completed | 283 ms |
| 3 days ago | Handshake completed | 284 ms |
| 4 days ago | Handshake completed | 294 ms |
| 5 days ago | Handshake completed | 442 ms |
| 6 days ago | Handshake completed | 283 ms |
| 9 days ago | Handshake completed | 277 ms |
| 11 days ago | Handshake completed | 490 ms |
| 14 days ago | Handshake completed | 338 ms |
| 16 days ago | Handshake completed | 334 ms |
| 18 days ago | Handshake completed | 335 ms |
| 20 days ago | Handshake completed | 320 ms |
| 22 days ago | Handshake completed | 309 ms |
| 24 days ago | Handshake completed | 315 ms |
| 26 days ago | Handshake completed | 300 ms |
| 27 days ago | Handshake completed | 324 ms |
| 29 days ago | Handshake completed | 327 ms |
The last 18 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 Computer-Use Agents API and makes no claim about it beyond what these checks measured.