Remote MCP · Endpoint
TeamUp MCP by usefulapi MCP server
Yes, as of 2 hours ago: the server returned an HTTP error.
DownLast checked 2 hours ago
Server URL
https://goteamup.usefulapi.io/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.usefulapi/goteamup
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 71.4% from 14 checks
- Described by its publisher as
- Check classes, attendance, customers, memberships and invoices in TeamUp and register customers.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Handshake completed | 135 ms |
| 4 days ago | Handshake completed | 182 ms |
| 6 days ago | Handshake completed | 242 ms |
| 8 days ago | Handshake completed | 246 ms |
| 10 days ago | Handshake completed | 220 ms |
| 12 days ago | Handshake completed | 190 ms |
| 14 days ago | Handshake completed | 266 ms |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 16 days ago | Handshake completed | 378 ms |
| 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 | Handshake completed | 371 ms |
| 24 days ago | Handshake completed | 245 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 TeamUp MCP by usefulapi and makes no claim about it beyond what these checks measured.