Remote MCP · Endpoint

Wakatime MCP server

No. Wakatime answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/wakatime/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/wakatime
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
109 ms
Tools exposed
56 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
WakaTime MCP.
Listing
From the official MCP registry (active).
Recent checks of Wakatime
CheckedResultHandshake
2 hours agoHandshake completed109 ms
20 hours agoHandshake completed1.89 s
2 days agoHandshake completed84 ms
3 days agoHandshake completed147 ms
4 days agoHandshake completed63 ms
5 days agoHandshake completed204 ms
6 days agoHandshake completed107 ms
8 days agoHandshake completed108 ms
11 days agoHandshake completed68 ms
13 days agoHandshake completed97 ms
16 days agoHandshake completed89 ms
18 days agoHandshake completed77 ms
20 days agoHandshake completed53 ms
22 days agoHandshake completed64 ms
24 days agoHandshake completed57 ms
26 days agoFailed - the request timed out—
27 days agoHandshake completed68 ms
29 days agoHandshake completed420 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.

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 Wakatime and makes no claim about it beyond what these checks measured.