Remote MCP · Endpoint
aiworker-data MCP server
Yes, as of 1 hour ago: the request timed out.
DownLast checked 1 hour ago
Server URL
https://aiworker.duckdns.org/mcp
The last check failed: the request timed out.
- Registry name
- org.duckdns.aiworker/aiworker-data
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 21 tools
- Uptime, last 30 days
- 82.4% from 17 checks
- Described by its publisher as
- Paid x402 tools (USDC per call): defi_yields, defi_protocol, scrape_markdown, scrape_summary.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the request timed out | — |
| 2 days ago | Failed - the request timed out | — |
| 4 days ago | Failed - the request timed out | — |
| 5 days ago | Handshake completed | 458 ms |
| 7 days ago | Handshake completed | 1.29 s |
| 8 days ago | Handshake completed | 615 ms |
| 9 days ago | Handshake completed | 486 ms |
| 12 days ago | Handshake completed | 778 ms |
| 13 days ago | Handshake completed | 528 ms |
| 15 days ago | Handshake completed | 479 ms |
| 17 days ago | Handshake completed | 515 ms |
| 18 days ago | Handshake completed | 488 ms |
| 19 days ago | Handshake completed | 483 ms |
| 20 days ago | Handshake completed | 782 ms |
| 21 days ago | Handshake completed | 483 ms |
| 21 days ago | Handshake completed | 494 ms |
| 23 days ago | Handshake completed | 487 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 aiworker-data and makes no claim about it beyond what these checks measured.