Remote MCP · Endpoint

wcway MCP server

No. wcway answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://wcway.com/mcp

The last check completed an MCP handshake.

Registry name
com.wcway/wcway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
112 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find the nearest public toilet worldwide. Read-only tools, no account, no API key.
Website
https://wcway.com/agents.md
Repository
https://github.com/ArneFfm/wcway-agents
Listing
From the official MCP registry (active).
Recent checks of wcway
CheckedResultHandshake
1 hour agoHandshake completed112 ms
2 days agoHandshake completed71 ms
5 days agoHandshake completed189 ms
7 days agoHandshake completed49 ms
9 days agoHandshake completed136 ms
11 days agoHandshake completed125 ms
13 days agoHandshake completed84 ms
15 days agoHandshake completed358 ms
17 days agoHandshake completed57 ms
19 days agoHandshake completed246 ms
20 days agoHandshake completed274 ms
21 days agoHandshake completed587 ms
23 days agoHandshake completed251 ms

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.

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