Remote MCP · Endpoint
TaScan MCP server
No. TaScan answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://app.tascan.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.snowbikemike/tascan-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 247 ms
- Tools exposed
- 106 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- 36 MCP tools for projects, tasks, workers, QR/NFC tags, and AI remediation. Task. Scan. Done.
- Website
- https://tascan.io/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 247 ms |
| 2 days ago | Handshake completed | 396 ms |
| 4 days ago | Handshake completed | 502 ms |
| 5 days ago | Handshake completed | 212 ms |
| 7 days ago | Handshake completed | 210 ms |
| 8 days ago | Handshake completed | 764 ms |
| 9 days ago | Handshake completed | 169 ms |
| 12 days ago | Handshake completed | 217 ms |
| 13 days ago | Handshake completed | 285 ms |
| 15 days ago | Handshake completed | 299 ms |
| 17 days ago | Handshake completed | 206 ms |
| 18 days ago | Handshake completed | 191 ms |
| 19 days ago | Handshake completed | 190 ms |
| 20 days ago | Handshake completed | 272 ms |
| 20 days ago | Handshake completed | 204 ms |
| 21 days ago | Handshake completed | 271 ms |
| 23 days ago | Handshake completed | 225 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 TaScan and makes no claim about it beyond what these checks measured.