Remote MCP · Endpoint
com.htagai/htag-docs MCP server
No. com.htagai/htag-docs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.htagai.com/mcp/v1/servers/htag-docs/mcp
The last check completed an MCP handshake.
- Registry name
- com.htagai/htag-docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 265 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 265 ms |
| 2 days ago | Handshake completed | 663 ms |
| 4 days ago | Handshake completed | 657 ms |
| 5 days ago | Handshake completed | 653 ms |
| 7 days ago | Handshake completed | 662 ms |
| 8 days ago | Handshake completed | 649 ms |
| 9 days ago | Handshake completed | 648 ms |
| 12 days ago | Handshake completed | 255 ms |
| 13 days ago | Handshake completed | 702 ms |
| 15 days ago | Handshake completed | 260 ms |
| 16 days ago | Handshake completed | 710 ms |
| 17 days ago | Handshake completed | 716 ms |
| 18 days ago | Handshake completed | 270 ms |
| 19 days ago | Handshake completed | 451 ms |
| 20 days ago | Handshake completed | 671 ms |
| 21 days ago | Handshake completed | 687 ms |
| 22 days ago | Handshake completed | 252 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 com.htagai/htag-docs and makes no claim about it beyond what these checks measured.