Remote MCP · Endpoint
Dol M1 MCP server
No. Dol M1 answered an MCP handshake 17 minutes ago.
UpLast checked 17 minutes ago
Server URL
https://gateway.pipeworx.io/dol-m1/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.pipeworx-io/dol-m1
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 72 ms
- Tools exposed
- 46 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- DOL Form M-1 — multiple employer welfare arrangement (MEWA) filings
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 17 minutes ago | Handshake completed | 72 ms |
| 9 days ago | Handshake completed | 168 ms |
| 9 days ago | Handshake completed | 96 ms |
| 11 days ago | Handshake completed | 208 ms |
| 12 days ago | Handshake completed | 176 ms |
| 13 days ago | Handshake completed | 129 ms |
| 14 days ago | Handshake completed | 123 ms |
| 15 days ago | Handshake completed | 657 ms |
| 16 days ago | Handshake completed | 198 ms |
| 19 days ago | Handshake completed | 56 ms |
| 21 days ago | Handshake completed | 1.28 s |
| 24 days ago | Handshake completed | 2.28 s |
| 26 days ago | Handshake completed | 2.57 s |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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 Dol M1 and makes no claim about it beyond what these checks measured.