Remote MCP · Endpoint
Trengo MCP by usefulapi MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://trengo.usefulapi.io/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.usefulapi/trengo
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 24 tools
- Uptime, last 30 days
- 50.0% from 14 checks
- Described by its publisher as
- Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
- Website
- https://usefulapi.io/trengo/
- Repository
- https://github.com/m190/usefulapi-mcp
- 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 | 209 ms |
| 4 days ago | Handshake completed | 153 ms |
| 6 days ago | Handshake completed | 151 ms |
| 8 days ago | Handshake completed | 263 ms |
| 10 days ago | Handshake completed | 279 ms |
| 12 days ago | Handshake completed | 188 ms |
| 14 days ago | Handshake completed | 282 ms |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 16 days ago | Failed - the check failed for an unclassified reason | — |
| 18 days ago | Failed - the check failed for an unclassified reason | — |
| 20 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 24 days ago | Failed - the check failed for an unclassified reason | — |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 7 responding of 14.
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 Trengo MCP by usefulapi and makes no claim about it beyond what these checks measured.