Remote MCP · Endpoint

TaskLite MCP server

No. TaskLite answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.tasklite.net/mcp

The last check completed an MCP handshake.

Registry name
net.tasklite/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
272 ms
Tools exposed
58 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
tasklite.net: hosted backend, REST API and admin for apps built by AI agents
Listing
From the official MCP registry (active).
Recent checks of TaskLite
CheckedResultHandshake
1 hour agoHandshake completed272 ms
2 days agoHandshake completed243 ms
4 days agoHandshake completed134 ms
5 days agoHandshake completed224 ms
7 days agoHandshake completed229 ms
8 days agoHandshake completed159 ms
9 days agoHandshake completed301 ms
12 days agoHandshake completed235 ms
13 days agoHandshake completed234 ms
15 days agoHandshake completed248 ms
17 days agoHandshake completed231 ms
18 days agoHandshake completed224 ms
19 days agoHandshake completed132 ms
20 days agoHandshake completed237 ms
21 days agoHandshake completed240 ms
21 days agoHandshake completed245 ms
23 days agoHandshake completed237 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 TaskLite and makes no claim about it beyond what these checks measured.