Remote MCP · Endpoint
network.waymark/server MCP server
No. network.waymark/server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.waymark.network/mcp
The last check completed an MCP handshake.
- Registry name
- network.waymark/server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 659 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Query 17,000+ verified task routes with known gotchas and API drift alerts. Free keyless reads.
- Website
- https://waymark.network/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 659 ms |
| 1 day ago | Handshake completed | 462 ms |
| 2 days ago | Handshake completed | 611 ms |
| 3 days ago | Handshake completed | 494 ms |
| 4 days ago | Handshake completed | 606 ms |
| 5 days ago | Handshake completed | 480 ms |
| 6 days ago | Handshake completed | 1.09 s |
| 8 days ago | Handshake completed | 565 ms |
| 11 days ago | Handshake completed | 1.07 s |
| 13 days ago | Handshake completed | 629 ms |
| 16 days ago | Handshake completed | 853 ms |
| 18 days ago | Handshake completed | 853 ms |
| 20 days ago | Handshake completed | 566 ms |
| 22 days ago | Handshake completed | 700 ms |
| 24 days ago | Handshake completed | 510 ms |
| 26 days ago | Handshake completed | 698 ms |
| 27 days ago | Handshake completed | 914 ms |
| 29 days ago | Handshake completed | 808 ms |
| 29 days ago | Handshake completed | 609 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 network.waymark/server and makes no claim about it beyond what these checks measured.