Remote MCP · Endpoint
Tailscale MCP by usefulapi MCP server
No. Tailscale MCP by usefulapi answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://tailscale.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/tailscale
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 287 ms
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 70.6% from 17 checks
- Described by its publisher as
- Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 287 ms |
| 2 days ago | Handshake completed | 339 ms |
| 4 days ago | Handshake completed | 322 ms |
| 5 days ago | Handshake completed | 159 ms |
| 7 days ago | Handshake completed | 218 ms |
| 8 days ago | Failed - the check failed for an unclassified reason | — |
| 9 days ago | Failed - the check failed for an unclassified reason | — |
| 12 days ago | Failed - the check failed for an unclassified reason | — |
| 13 days ago | Handshake completed | 312 ms |
| 15 days ago | Failed - the check failed for an unclassified reason | — |
| 17 days ago | Failed - the check failed for an unclassified reason | — |
| 18 days ago | Handshake completed | 48 ms |
| 19 days ago | Handshake completed | 178 ms |
| 20 days ago | Handshake completed | 248 ms |
| 21 days ago | Handshake completed | 294 ms |
| 21 days ago | Handshake completed | 208 ms |
| 23 days ago | Handshake completed | 236 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Tailscale MCP by usefulapi and makes no claim about it beyond what these checks measured.