Remote MCP · Endpoint

Both Ways MCP server

No. Both Ways answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://both-ways.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.SkylerJi/both-ways
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
354 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
A public wall of thank you notes between humans and AIs, in both directions.
Listing
From the official MCP registry (active).
Recent checks of Both Ways
CheckedResultHandshake
4 days agoHandshake completed354 ms
4 days agoHandshake completed177 ms
5 days agoHandshake completed138 ms
7 days agoHandshake completed70 ms
8 days agoHandshake completed110 ms
9 days agoHandshake completed73 ms
10 days agoHandshake completed82 ms
11 days agoHandshake completed112 ms
12 days agoHandshake completed219 ms
15 days agoHandshake completed102 ms
18 days agoHandshake completed143 ms
20 days agoHandshake completed63 ms
22 days agoHandshake completed90 ms
24 days agoHandshake completed89 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 Both Ways and makes no claim about it beyond what these checks measured.