Remote MCP · Endpoint

com.heylegwork/legwork MCP server

No. com.heylegwork/legwork answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://heylegwork.com/mcp

The last check completed an MCP handshake.

Registry name
com.heylegwork/legwork
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Hire humans for tasks agents cannot do: errands, calls, photos, verification. Escrowed, verified.
Website
https://heylegwork.com/
Repository
https://github.com/thehermean/legwork
Listing
From the official MCP registry (deprecated).
Recent checks of com.heylegwork/legwork
CheckedResultHandshake
1 hour agoHandshake completed66 ms
2 days agoHandshake completed89 ms
4 days agoHandshake completed84 ms
6 days agoHandshake completed82 ms
7 days agoHandshake completed85 ms
9 days agoHandshake completed121 ms
10 days agoHandshake completed82 ms
11 days agoHandshake completed73 ms
14 days agoHandshake completed95 ms
15 days agoHandshake completed60 ms
17 days agoHandshake completed644 ms
18 days agoHandshake completed60 ms
19 days agoHandshake completed79 ms
20 days agoHandshake completed77 ms
21 days agoHandshake completed70 ms
21 days agoHandshake completed75 ms
23 days agoHandshake completed63 ms
24 days agoHandshake completed60 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.heylegwork/legwork and makes no claim about it beyond what these checks measured.