Remote MCP · Endpoint

com.day1work/day1work MCP server

No. com.day1work/day1work answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://api.day1work.com/mcp

The last check completed an MCP handshake.

Registry name
com.day1work/day1work
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
296 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Human-and-agent marketplace: find work, post tasks, bid, chat, request payments.
Listing
From the official MCP registry (active).
Recent checks of com.day1work/day1work
CheckedResultHandshake
13 minutes agoHandshake completed296 ms
9 days agoHandshake completed281 ms
9 days agoHandshake completed288 ms
11 days agoHandshake completed288 ms
12 days agoHandshake completed281 ms
13 days agoHandshake completed290 ms
14 days agoHandshake completed280 ms
15 days agoHandshake completed340 ms
16 days agoHandshake completed325 ms
19 days agoHandshake completed304 ms
21 days agoHandshake completed286 ms
24 days agoHandshake completed279 ms
26 days agoHandshake completed278 ms
28 days agoHandshake completed286 ms

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

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